My last example of controlling a sequence to test some default-behavior was not “well-testable” PL/SQL code.
In this example I show how we can achieve a method that is much easier to test, doesn’t require touching internals – all without changing the public API of the method.
A combination of Package global state and Package invalidation can easily lead to ORA-04061 errors, especially in unit-testing situations.
This blog-post explains the problem and shows possible solutions (all with examples)
Unit-Tests are automated checks of certain behavior. But what if we could also use them to describe what the functionality they’re checking is supposed to do?
How to explore some functionality you don’t know but want to change or improve?
Write a unit test with utPLSQL and use the force-manual-rollback param!
#ThanksOGB
How to concatenate a list of Strings in PL/SQL?
This blog-post shows 4 different approaches.
Object Types are a very useful thing when used in PL/SQL, but Oracle even allows us to have them inside a table.
Let’s see how we can put the numeric_strucutre-logic inside the Force Powers table and use indizes on the new column.
Modern SQL and especially PL/SQL is turing complete and can be used to solve every problem, but Oracle SQL Types can help greatly to do it in a much more readable way.
Did you know you can narrate the story of the Star Wars movies with utPLSQL annotations?
In this blog post I show you how and list 4 takeaways you might not have known.
Comparing the results of 2 queries is a task more complicated than I thought initially.
I show some more pitfalls of the MINUS approach (which I still find convenient in some cases) and alternatives.
The context-feature of #utPLSQL can greatly help to organize your tests and reduce the setup/teardown time of tests.
Learn how to use them to test the Deathstar security system.
#100CodeExamples