Testing Tools and Techniques
Testing is a different approach to testing, focused on coordination, feedback, and application response. Tools like Spira 5.3 aid in managing sessions, logging steps, recording responses, and communicating with developers efficiently. Potential developments include integrating with mind-mapping tools, enhancing notifications, and aligning nomenclature with exploratory testing terminology
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Exploratory Testing Fundamentally different to other testing about feel and coordination, not managing a suite of regression tests Record application response Communicate with developers Get feedback to inform future testing Develop aims / charter Manage a session Log steps of tester
Where exploratory testing tools can help Develop aims / charter Quick creation of tests Manage a session Help record activity [eg screen recorder] Log steps of tester Quick and flexible editing of tests Record application response filter things down to the main findings [eg video editing] Actively alert the right people to review or take action [often not as formal as bug reports] Communicate with developers Get feedback to inform future testing Help the tester track and follow-up on actions
Where can Spira 5.3 help Develop aims / charter New exploratory test case type Dedicated exploratory testing experience for execution of a single exploratory test case Manage a session Log steps of tester On-the-fly editing (inc adding/removing test steps) Record application response Rich-text editing and great screenshot capture Communicate with developers A simple way to log multiple discoveries from a single test step Get feedback to inform future testing Help the tester track the latest on their different discoveries
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 application response Record additional activity during testing (beyond screenshots) Communicate with developers Further integrations with internal IM Get feedback to inform future testing Improve notifications, offering more options and
Our Proposed Workflow For SpiraTeam 5.3 Record application response Get feedback to inform future testing Develop aims / charter Manage a session Log steps of tester Communicate with developers Get ALERTS when tasks have been closed CREATE exploratory test case EXECUTE the test case with new UI EDIT RECORD the test run status as normal Create TASKS as light touch issues everything on the fly
Ability to make / use exploratory test could be linked to permissions
Technical questions CREATE EXECUTE EDIT RECORD TASKS ALERTS Link to permissions? Include sample data? Any missing actions? See actual result from last run? Link of actual result to tasks? (1 to many or 1 to 1)? When to test again? (see below) See status from last run?
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?
