Best Practicies & Success Stories
When we create our programs, just getting it to compile is not enough. We want to test if our code does what it is supposed to do. But testing over and over again is time consuming and mostly boring process. You don’t want to run the same tests over and over again. It worked before, so it will work now, or won’t it? This should be an automated process which you can start whenever you want, even when you’re not present. There are multiple unit testing frameworks and tools available to do this job for you. This session will show a couple of them and will show an in depth analysis of utPLSQL and SQL Developer. Although very different in approach then can both be useful in your development process. We’ll discuss the structure of unit testing: - Setup - Run - Validate - Teardown Then we’ll demonstrate the two products. On the one hand we will see how easy it is to setup utPLSQL and start using it, but also the technical, programmatic, approach that suites developers. On the other hand there is SQL Developer with a more declarative approach to describe and run your tests. We will also see how this can be integrated in a Continuous Delivery method with automated testing. When you are using a unit testing framework then you can be confident you are done programming and your program is working correctly.