Furthermore, in order to run exploratory testing in a Waterfall environment,documentation on test results is a must and this documentation should be easy totrace back to requirements. Of course, this type of documentation is always useful inany environment.What does adoption entail?Embracing exploratory testing is relatively easy, as it isquick to launch (and scale), simple to learn and provides benefits for the entire team.That said, it’s important to keep in mind that it should not be the only form of testing(rather, it should inform what type of testing happens next). Additionally, even thoughit’s unscripted, exploratory testing should not be unstructured (testers still need to seta goal, log your activities and take on the mindset of a specific user persona).Who is it for?Exploratory testing can help reduce time spent testing, find moredefects and improve code coverage. As a result, exploratory testing is best suited forteams that are under time constraints, teams that need help identifying the besttypes of tests to run (especially in cases where there are no specifications fromdevelopers) and teams that want to make sure they didn’t miss anything in previoustests. Key team members who should be involved in exploratory testing include:Testers (although everyone on the team should participate in some way)What are best practices?Best practices for testers using exploratory testinginclude:Organizing the functionality in the application using something like a Mindmapor a spreadsheetFocusing on certain areas or certain scenariosTracking what gets tested to help reproduce any errorsDocumenting results in a toollike qTest Explorerso there is someaccountability for what got tested
4) Session Based TestingWhat is it?Finally, let’s review session based testing. Session based testing buildson exploratory testing by providing more structure. Because exploratory testing iscompletely unscripted, it makes accountability difficult and relies heavily on the skillsand experience of the tester(s) involved. Session based testing aims to ease someof these shortcomings by bringing more structure to exploratory testing withouttaking away from the benefits that exploratory testing provides, such as the ability tobetter mimic the user experience and get creative with testing.Session based testing provides this structure by conducting testing during time-boxed, uninterrupted sessions, testing against a charter and requiring testers toreport on the testing that took place during each session. Additionally, session basedtesting should be capped off witha “debrief” between the tester(s) and the managerthat covers the five PROOF points: What happened (Past), what was achieved(Results), what got in the way (Obstacles), what still needs to be done (Outlook) andhow does the tester feel about it (Feelings).
Upload your study docs or become a
Course Hero member to access this document
Upload your study docs or become a
Course Hero member to access this document
End of preview. Want to read all 82 pages?
Upload your study docs or become a
Course Hero member to access this document
Term
Fall
Professor
NoProfessor
Tags
