It’s been more than 5 months since I started at Quality Minds and shifted from working as a software developer to a quality engineering consultant. I thought I would soon be doing a lot of test automation, using Cypress or Playwright, but instead of that, something totally different happened
There is a vast amount of different terms to describe tests, and especially developers can easily struggle with their specific meaning or what the term tries to emphasize.
In this post I try to give an overview about different aspects that are used to categorize and describe tests as a tool to improve one of most effective, frightening and impactful actions in software development: Talking to each other.
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!