The last few months, I’ve had the pleasure of using utPLSQL v3, a unit testing framework for PL/SQL, on a new project that I’m working on. Sure – writing tests takes a bit extra time, but it’s such a huge help when you’re constantly refactoring a system that grows from zero.
This week, I had a new use case: We had to move our test-system to a new cloud account. (Yes we’re running everyting on Oracle Cloud). After we had done the transition, I ran my unit tests as a smoke test to see if everything in the database was in place. I spotted a couple of missed job-definitions, got them installed and reran the tests to verify that everything was ok. Thanks to the tests, the transition went very smooth.
Jacek Gebal, whom I had the pleasure of getting a utPLSQL shirt from at the OUG Ireland conference, and his fellow contributors have really done a great job on this and has really lowered the threshold for doing unit-testing for database code!
Test your code – not you patience!