At my first ever project, I was one of the UAT testers for an internal application (only business user facing), where you would have to create different types of profiles (for people or for organisations) and then later edit those profiles or use those profiles to do certain things (I can’t be too specific sorry).
The approach we took was to write test cases based on the requirements and then when the SUT (Software Under Test) was ready, we would then execute those test cases.
Continue reading “Bloggers Club: What’s the most fun you’ve had with a bug”
For the past seven months, since I came back from maternity leave, I’ve spent the majority of my time focussing on test automation. I have both set up a test automation framework as well as overhauled two existing test automation frameworks for mobile (both Android and iOS).
But one of the struggles I have faced is not getting lost as to fail to see the forest for the trees. During the day to day, it can be easy to be constantly knee deep in code and forget the problem I am actually trying to solve. Why am I actually doing test automation in the first place?
Continue reading “Tackling Test Automation Part I: What problem are you trying to solve?”