It is a dark time for agile database developers of the imperial army. The sith-lords in charge constantly urge to just implement the functionality and not waste time with development of automated self-tests.
Convinced of the importance of his mission, a single, fearless database developer starts a dangerous attempt to make automated self-tests a natural part of the development process and has to meet numerous challenges around integrated commits, complex selects and unknown functionality in the process.
This presentation with many practical examples and live-demos provides answers to some of the most frequent questions and challenges that come up during adoption of automated self-tests, especially in the database.
We will see the practical usage of many features of the open-source framework utPLSQL but also consider fundamental challenges around the topic of “automated tests”.
-
-
- How much additional development time do I need when I create unit-tests?
- What even is an automated test and how does it work?
- How do I get started with utPLSQL?
- How can I write tests for complex data structures?
- What tests should I automate?
-
How can I practically integrate automated self-tests into my development process?
-
