#100CodeExamples
Narrate Star Wars Movies with utPLSQL annotations
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.
#100CodeExamples
Testing the Deathstar security with utPLSQL contexts
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
#100CodeExamples
#100CodeExamples – Test updatable views with utPLSQL Cursors
If it comes to testing updatable views, the use of nested tables from ROWTYPE records in combination with utPLSQL’s cursor comparison is invaluable.
#100CodeExamples
#100CodeExamples – utPLSQL Cursor Comparison with user-defined Types
#100CodeExamples: Cursor-comparison is one of the most powerful features of utPLSQL.
To model our expectation, we can not only use SELECT FROM DUAL but also the much more powerful user-defined types and Nested Table-collections.
#100CodeExamples
#100CodeExamples – SYSDATE vs. CURRENT_DATE
#100CodeExamples – SYSDATE vs. CURRENT_DATE
I had a very strange problem yesterday where #utPLSQL cli showed different test outcomes than running the tests from my IDE. Here’s the reason.
#100CodeExamples
#100CodeExamples – utPLSQL’s Suite Hierarchy in action
#100CodeExamples – utPLSQL’s Suite Hierarchy in action.
A great tool to structure tests, avoid duplication, give context and improve performance.
#100CodeExamples
#100CodeExamples – Unit-Tests for Primary/Secondary Lookup with Cursor Comparison
#100CodeExamples – Unit-Tests for Primary/Secondary Lookup with the Cursor Comparison capabilities of utPLSQL.
Reflections
DOAG 2018 – my personal review
My personal review of DOAG 2018 as both, first-time attendee and first-time speaker.
Uncategorized
Open Source engagement for utPLSQL
Why I didn’t blog for several weeks: Open Source engagement for @utPLSQL.
Uncategorized
Strongholds of confidence: self-testing your database
No software is perfect and we should create meaningful, automated self-tests to give us the confidence in continuously changing and improving our software.