Whenever one of family members asks me what I do, my simple response is "Eh, I check if things work". Most of the time, it's a good enough TL;DR of my role in QA world. I would also replace things with different words based on the individuals understanding of software.
But when they ask for more details, well ... that's where they lose interest.
So, it only made sense for me present my thoughts and actions in a diagram!
This will be a 3-part series containing a set of inputs, outputs, decisions and options to progress, with the end goal being to successfully diagnose the root cause of an issue I encounter.
App: A common web app, let's call it dev.to
Test case: Successfully update user details
Part 2 coming soon.
Top comments (0)