Quality assurance traditionally entailed only of teams evaluating the code and ensuring that nothing was breaking or performing abnormally. In these setups, there wasn’t time to worry about how end users would take it, it just mattered that the app would work. However, in today’s world of endless software, quality assurance must make the customer the priority driving their work. Thinking like the customer is going to be crucial for QA teams for a few important reasons:
The general concept of software QA is fairly straightforward: to ensure that the solution is truly ready for market. However, this is easier said than done. Devising a test management strategy that adequately vets a solution and filters out potential defects demands a concerted effort from testers as well as the developers they will be working with (assuming a DevOps mentality).
As I wrote in various articles, organization is one of the 3 key requisites for successful automated testing, the other two being test design and automation architecture.
I was reading an article a few months ago entitled, “is Silicon Valley the next Detroit…”, and I found it very interesting.