How do software development teams make sure the products they release are of high quality?
Not so long ago, a cynical answer to this question would have been something like, “Since when did software development teams care about quality?” It’s unfair, but it’s rooted in perceived quality issues from all types of development teams, from “lone wolf” contract developers to giant software conglomerates.
Software is complex stuff. Even relatively straightforward applications that do only a few things can have a dizzying number of possible “journeys” for users to take. Ideally, every one of those journeys is tested under all possible circumstances to ensure the software works as expected and doesn’t crash, pop-up useless error messages, or provide wrong answers.
