The Last Pieces of the Puzzle
Once the candidate tests pass, the code leaves the test group and is placed in an internal staging environment. We use our own softwareâthe wiki on stagingâto essentially run our business.[91] We use it to create project plans, to track the iteration, to do QA tracking, and to create stories, for blogging and communication. That way, staging becomes the final proving ground for our software before it goes into production, and our employees occasionally do find defects or, more likely, usability issues or performance issues that unit and functional testing did not uncover.
Our entire testing puzzle includes feature testing, wikitests, running test plans, exploratory testing, getting feedback from staging, usability, story review, beta programs, logging and log evaluation, and occasional performance research. If we tried to do everything and do it well, our team would swell in size and make the company unviableâor it would simply burn out the staff very quickly. Instead, we have to ask how much is enough and what can we trade out.
Our goal is not to know exactly what the software can do, but instead to provide a rapid assessment of the software that is fit for purpose. A few key questions I havenât mentioned yet are: âWhat should I be doing right now?â and âAm I done yet?â
Again, those are philosophical questionsâquestions of aesthetics. I would posit that combinations of the puzzle pieces that look the most beautiful are probably the correct ...
Get Beautiful Testing now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.