How to automate over 18 000 test cases in two years while keeping maintenance workload under 15 per cent - 14,3% to be exact. The system under test was a tax processing software. Despite several attempts, no one could successfully automate testing on this system earlier.
Pekka Klärck is the main developer behind Robot Framework, the open source test automation and RPA framework. Pekka shares how he was inspired to start developing exceptionally usable automation framework valued by thousands.
It was late 2005. I was preparing for my new job at Qentinel, a small software quality assurance shop. My future team members were each presenting those big, important, and exciting things they thought I should know before I officially start as the CEO of Qentinel in January 2006.
At 16th of February 2021 we received a message late in the evening from one of our developers that one of our build pipelines was failing mysteriously and without clear cause, when fetching our own internal libraries. “That’s strange, as nothing should have been changed in the last week in those libraries”. I remember thinking.
Test architecture means the way you put together all those things you need in testing. Depending on what you test, where, and how, the test architecture may be simple or complex, ad-hoc or well-thought. Most often than not, test architectures are not thought of, they just emerge.