Exploratory Testing Fundamentally different to other testing – about feel and coordination, not managing a suite of regression tests Develop aims / charter Manage a session Log steps of tester Record application response Communicate with developers Get feedback to inform future testing

Where exploratory testing tools can help Quick creation of tests Develop aims / charter Help record activity [eg screen recorder] Manage a session Quick and flexible editing of tests Log steps of tester filter things down to the main findings [eg video editing] Record application response Actively alert the right people to review or take action [often not as formal as bug reports] Communicate with developers Help the tester track and follow-up on actions Get feedback to inform future testing

Where can Spira 5.3 help New exploratory test case type Develop aims / charter Dedicated exploratory testing experience for execution of a single exploratory test case Manage a session On-the-fly editing (inc adding/removing test steps) Log steps of tester Rich-text editing and great screenshot capture Record application response A simple way to log multiple discoveries from a single test step Communicate with developers Help the tester track the latest on their different discoveries Get feedback to inform future testing

Potential areas for future development Change internal nomenclature to reflect exploratory testing terminology Develop aims / charter Running an exploratory test set (an exploratory test case within a test set could be available for regression testing in 5.3) Manage a session Integrate with tools like mind-maps for capturing a testing session Log steps of tester Record additional activity during testing (beyond screenshots) Record application response Further integrations with internal IM Communicate with developers Improve notifications, offering more options and Get feedback to inform future testing

Our Proposed Workflow For SpiraTeam 5.3 Develop aims / charter Manage a session Log steps of tester Record application response Communicate with developers Get feedback to inform future testing CREATE exploratory test case EXECUTE the test case with new UI EDIT everything on the fly RECORD the test run status as normal Create TASKS as light touch issues Get ALERTS when tasks have been closed

Ability to make / use exploratory test could be linked to permissions

Technical questions Link to permissions? Include sample data? Any missing actions? See actual result from last run? See status from last run? Link of actual result to tasks? (1 to many or 1 to 1)? When to test again? (see below) CREATE EXECUTE EDIT RECORD TASKS ALERTS

Other technical issues CREATE EXECUTE EDIT RECORD TASKS ALERTS SpiraTeam only, or SpiraTest too but without tasks? What options on finishing a test run? E.G.: create new test case from run, update existing test case, do neither? Should tasks be linked to both the test run and test case or just the test run? Change the test case status when all tasks completed? A progress bar of tasks on the Test Case list page?