Move Introduction
Open Introduction
Navigating the World as a Context-Driven Tester provides responses to common questions and statements about testing from a context-driven perspective.
The e-book was designed to act as an FAQ for the day-to-day situations a tester may find themselves in and how to approach them from a context-driven perspective.
The book was coordinated and collated by testing practitioner and long-standing AST member Dr Lee Hawkins. The content was crowdsourced, starting early in 2021 and the final edit was made in August 2024 after some 28 requests for contributions. These requests were made across multiple platforms, including Twitter (X), LinkedIn, Slack (viz. in the AST and Rapid Software Testing channels), Mastodon and the AST mailing list. All contributions are attributed.
Introduction
118 words
Move Testing
Open Testing
How can I possibly test "all the stuff" every iteration?
It's never possible to test "all the stuff" because there are so many variables involved in running any piece of software anywhere that there's always another test that could be performed. What is possible, though, is to decide what is the important stuff to test given what we know about stakeholder concerns, risks to business value, time available, the software, and other relevant factors.
Firstly, does every single feature or area of the software really get changed every single iteration? The whole point of iterating over software during the development is to introduce small, but valuable changes and deliver them to users. Since the changes are small, most of the software is the same as it was in the last iteration and therefore does not need to undergo comprehensive testing again.
Secondly, you need to determine the level of risk introduced by these changes. What is being done to the software that introduces so much risk every iterat
Testing
2,962 words