In a perfect world, our dev teams would publish flawless codification and never create a single misunderstanding (though I suppose I might be out of a job so.) The truth of the thing is software never is staring. Mistakes, like Thanos, are inevitable. Moreover, testers shouldn ’ t be attempting to get the software perfect, exactly mitigate risk by protect taxation and the client experience.

When we regard the overall customer experience this go easy to realise. A tester shouldn ’ t expend all of their time just searching for defects. A typographical error might be unpleasant, but it ’ s certainly not as significant as a security flaw. You need a risk-based approach toward protect the marque that covers the virtually significant parts of the package.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Here ’ s more on what you should test and how to prioritize the customer experience above all else.

video

Look for part 3 next workweek, where I ’ ll continue the human element of testing.