The main goal of endgame testing is to test the system end to end from the user's perspective. This should ensure continuity between components developed by different teams, continuity in user experience, and successful integration of new features. Endgame testing will often identify gaps that are difficult to discover inside agile teams, including flows across the product.
Is testing about checking against system requirements, or is it about exploring the software? In this article, Elisabeth Hendrickson explains a valuable truth often clouded by this debate—good testing takes advantage of both of these approaches.
Lisa Crispin explains in this article how CI has become an absolute necessity for any software development team in this day and age. For those who have yet to fully embrace CI, this article gives you some great reasons you should, along with some helpful resources to get you started.
As a test professional in waterfall, I was used to getting the code much later and buggier than I expected and being under tremendous pressure to finish my testing before the go-live date hit. Then one day, I found out that there was a better way. Testers could be involved much earlier in the lifecycle, they could participate in requirements and design decisions as they happened, and the code could actually be unit tested before I received it! Heaven? Nope, agile.
Exploratory testers design and execute tests in the moment, starting with an open mission and investigating new ideas as they arise. But how do we know when to stop? The first step is to recognize that we can't know when we're done, because any approach to answering the stopping question is necessarily heuristic.
Forget what you thought you knew about exploratory testing. Dion Johnson is disturbed by its exploitation by those who wish to escape accountability and forgo up-front planning, but says that exploratory testing and scripted testing can work together to enhance quality practices.
Among the hardest things to explain is something that everyone already knows. We all know how to listen, how to read, how to think, and how to tell anecdotes about the events in our lives. As adults, we do these things every day. Yet the level possessed by the average person of any of these skills may not be adequate for certain special situations.Exploratory tester James Bach describes eight key skills that expert explorers possess, and how you can develop them too.
In this interview, TechWell speaks with Bart Knaack, test advisor at Professional Testing, and his partner at the Test Lab, Wade Wachs. Bart gave a keynote at STARWEST titled "The Survival Guide for Testers and Test Managers."
In this interview, Penny Wyatt discusses her Agile Development Conference West session, "Transform Your Agile Test Process to Ship Fast with High Quality," to share some of the ways she and her team achieved success, and how they—and you—can continue to develop and grow together.
Matt Barcomb works at LeanDog where he is passionate about building collaborative cross-functional teams and finding ways to make the business-software universe a better place to work, play, and do business. Heather Shanholtzer talked to Matt about exploratory testing in an agile project.
The concept of exploratory testing is evolving, and different interpretations and variations are emerging and maturing. These range from the pure and original thoughts of James Bach, later expanded to session-based exploratory testing by Jon Bach, to testing tours described by James Whittaker, to the many different ways test teams across the world have chosen to interpret exploratory testing in their own contexts. Though it appears to be simple, exploratory testing can be difficult to introduce into a traditional organization where testers are familiar only with executing scripted test cases and where the concept of exploration and creative testing may be somewhat foreign. At the same time, organizations need to address the challenges of traceability and reporting, moving from traditional ways to a more exploratory approach.
Typical automated tests perform repetitive tasks quickly and accurately. However, with some creativity, you can leverage automation to dramatically increase its ROI. Doug Hoffman demonstrates how to employ test automation for testing activities that are impossible with manual testing.
Charters help you guide and focus exploratory testing. Well-formed charters help testers find defects that matter and provide vital information to stakeholders about the quality and state of the software under test. Rob Sabourin shares his experiences defining different exploratory testing charters for a diverse group of test projects. For example, reconnaissance charters focus on discovering application features, functions, and capabilities; failure mode charters explore what happens to applications when something goes wrong. In addition, you can base charters on what systems do for users, what users do with systems, or simply the requirements, design, or code. Rob reviews key elements of a well-formed testing charter-its mission, purpose, focus, understanding, and scope. Learn how to evolve a test idea into an exploratory charter using examples from systems testing, Scrum story testing, and developer unit testing.