Welcome to a better world!
In our world, participants in IT-projects have a better life.
- The developers are confident when refactoring or fixing the code.
- The developers are aware of that they make mistakes, and they are informed immediately when the do make mistakes.
- The developers are very productive and dare does major changes in the code.
- The testers are testing new features, instead of spending time on performing trivial repeatable tests.
- The test managers always know the status of the system under test, instead of just having a feeling.
And, IT projects have a higher success rate.
“Fail fast – Fail often” is the key
The definition of Regression testing:
Regression testing is a type of software testing that intends to ensure that changes (enhancements or defect fixes) to the software have not adversely affected it.
Regression testing is the most important test at all. It ensures that what was operating yesterday also operates today. Regression testing is where most of the system is tested and is often a test that takes a lot of time and resources, and it is trivial and boring to test the same things repeatedly.
That is probably why many projects fail to execute the regression test, by only executing a subset of the regression test cases. The reason is obvious, it allocates the lots of resources and the time is limited.
Automating the regression test ensures that all regression tests are executed, performed in a very limited time and with very few resources.
What are you waiting for
We know how, and we are good at it.
Over the last 20 years, we have experienced many IT-projects. We have been digging deep into several IT-systems, not trying to fix them directly, but ensuring that they work as intended. If any problem occurred we have found the root cause of the problem, giving the developers enough information to make the fix as fast as possible.
In every project, we have striven to have the system under test, tested as thoroughly and as fast as possible, to provide information to the developers to fix the defect found, while they still have their code fresh in mind.
Why not having fun while repeatedly executing the regression test and having it done fast and often, by automating the test execution and failing fast?
Why don’t you automate your tests?