Be the first to like this
Sometimes we test to find bugs.
Sometimes we test to comply with regulations.
Sometimes we test to answer a question for someone.
Sometimes we test because its what was done before.
Sometimes we’re not even sure what we are testing for, only that someone is paying us to “just test it”.
Whether or not someone has told us why we are testing, or what we are testing for, if we are being paid (or otherwise compensated) for testing, there is a reason that someone is willing to pay for that testing to be done. That reason is (or should be) our testing mission.
During this keynote, Scott Barber explores some of the most commonly assigned or assumed testing missions, shares his thoughts on contexts in which these missions may or many not be particularly valuable and, publicly for the first time, discusses a software product assessment model that he believes has the potential to dramatically improve the alignment of our assigned or assumed testing missions with the wants and needs of the businesses paying us to conduct that testing.