Skip to main content

Real World Testing of PL/SQL Code - An Office Hours Session

Since February 2019, I've been running, with Chris Saxon, on my team of Developer Advocates, monthly PL/SQL Office Hours sessions. They generally consist of short presentations on a PL/SQL-related topic, followed by lots of interesting discussion - between Chris and I, with attendees on the session, and with other speakers.

On November 5 at 9 AM Eastern, I am very pleased to have a session focused on testing PL/SQL code, featuring developers who are doing it out there in the "real world."

No application will ever have zero bugs, but you sure want to keep them to a minimum. The best way to do this is to implement automated regression tests of your code, but "best" as usual does not equate to "easiest." Building and managing tests can be a big challenge, so in this Office Hours session, we will hear from developers who are doing just that. Learn from your peers about the obstacles they faced and how they overcame them. Bring your own stories and your questions, and let's all work together on improving our code quality!

Our first presenter will be Jasmin Fluri.
Ms. Fluri is an independent consultant at Schaltstelle GmbH and lectures on software engineering and code review at the University of Applied Sciences North-western Switzerland. Her focus as a database developer and DevOps engineer lies on continuous integration and delivery pipelines, automation of recurring tasks, PL/SQL development, data engineering, and data warehousing.

We will then hear from Maik Becker and Swathi Ambati of Triology.
"We had a requirement where we used to write unit tests for legacy code and we used utPLSQL framework. We have developed an App to save test results and to run multiple tests at once without writing any execution code and also show the result in a very efficient manner. Since the project was an APEX App, we decided to use APEX as well to run tests and visualize results."

Deepthi Bandari, a senior software engineer at Fidelity Investments, will share some of her joys and challenges when it comes to unit testing, test automation and promoting engineering excellent.

And they are not all! We'll hear from Patrick Barel, who is a PL/SQL Developer for Qualogy in the Netherlands. Besides working with SQL and PL/SQL he wrote different plug-ins for PL/SQL Developer, publishes articles on his own blog and is an Oracle ACE Director. Patrick is going to show what he's been doing with SQL Developer unit testing features and SQLcl commands.


We will also be joined by Samuel Nitsche, one of the core maintainers of utPLSQL:
Samuel Nitsche is a curiosity-driven software-developer with nearly 20 years of development experience, working at Smart Enterprise Solutions GmbH, a small software company in southern Germany. In his free time he writes regularly about database development and testing topics, presents at meetups and conferences (gladly in sith-robe) and works on making the framework "even more awesome."

If you have been doing any kind of automated regression testing of your Oracle Database code, we'd love to hear from you, whether you are using SQL Developer integrated unit testing, utPLSQL, Quest Code Tester, another open source framework...or even (especially!) your own "homegrown" approach.

All our welcome. Please do get in touch if you'd like to present your experiences.

Subscribe for reminders at the PL/SQL Office Hours home page so that you can get email reminders about this and other sessions!

Comments

Popular posts from this blog

Three tips for getting started right with Oracle Database development

By "Oracle Database development", I mean, more or less, writing SQL and PL/SQL. I assume in this post that you have access to Oracle Database (which you can get via Cloud services, Docker , GitHub and OTN ). A. Use a powerful IDE, designed with database programming in mind. There are lots of editors out there, and many IDEs that work with Oracle Database. Sure, you could use Notepad, but OMG the productivity loss. You could also use a popular editor like Sublime, and then it get it working with Oracle. I suggest, however, that you  download  and install Oracle's own own, free, powerful IDE: SQL Developer . If you like to complement your graphical IDE with a command line tool (or OMG if you actually prefer  a command line tool to a graphical interface), you should also check out the relatively new and generating-lots-of-excitement SQLcl . B. Enable compile-time warnings and PL/Scope. The database has tons of useful functionality burned right into it, ready for...

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...

The future of Oracle PL/SQL: some thoughts on Sten Vesterli's thoughts

Sten Vesterli published a very thought-provoking post on his blog: Please stop reading this post, and read that one. When you are done, come on back here for my thoughts on Sten's thoughts. OK. You read it. Here we go. First, thanks, Sten, for being such an interesting, wise, sometimes provocative voice in our community. Next, Sten writes: Now, on the one hand, I certainly agree that the vast majority of young developers are currently caught up in the modern version of a Gold Rush, which is: "Build an app using JavaScript, pay no attention to that database behind the curtain." But I can assure you that I still do meet young PL/SQL programmers, regularly, when I am at conferences and doing onsite presentations at companies. So, young person who writes PL/SQL: do not be afraid! You are not alone! And you are super-smart to have made the choice you did. :-) Next, Sten offers this advice to managers: I agree that PL/SQL is a "spec...