Inflectra Customer Forums: Exploratory testing - modifying test steps and test cases during test run (Thread) When doing exploratory testing the tester always learns something new about the system, and wants to execute the test cases and improve the test cases simultaneously - that means: So the tester executes these tasks in parallel: - executes test cases - modifies/adds/removes test cases, executes tests that were added/modified - modifies/adds/removes test steps, executes test steps that were added/modified Can it be done in Spira? Now I see that when you run "Execute" of some Test Set - then all the tests are _copied_ to the test run, so when tester adds/modifies tests and steps - he/she cannot run them since new changes cannot be promoted to existing test run. Test Runs are like "cast in stone". As a result of test session - "Test Cases" part of the system contains added test cases and added test steps that were actually executed, some passed some failed - but nothing about them is in the Test Run part running SpiraTeam v4.2.0.7 en-US(C) Copyright 2006-2024 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/1534.aspxthreadId=1534Roman Fominych (rf@scientificgames.is)Exploratory testing - modifying test steps and test cases during test run When doing exploratory testing the tester always learns something new about the system, and wants to execute the test cases and improve the test cases simultaneously - that means: So the tester executes these tasks in parallel: - executes test cases - modifies/adds/removes test cases, executes tests that were added/modified - modifies/adds/removes test steps, executes test steps that were added/modified Can it be done in Spira? Now I see that when you run "Execute" of some Test Set - then all the tests are _copied_ to the test run, so when tester adds/modifies tests and steps - he/she cannot run them since new changes cannot be promoted to existing test run. Test Runs are like "cast in stone". As a result of test session - "Test Cases" part of the system contains added test cases and added test steps that were actually executed, some passed some failed - but nothing about them is in the Test Run part running SpiraTeam v4.2.0.7 Fri, 09 Sep 2016 10:23:57 -04002016-09-13T14:27:18-04:00/Support/Forum/spiratest/issues-questions/1534.aspxmessageId=2752Jim R (donotreply5@kronodesk.net) Hi Roman Yes that is correct, we make a copy of the test case called a 'test run' so that m Hi Roman Yes that is correct, we make a copy of the test case called a 'test run' so that multiple users can run the same test case without affecting each other. You can make changes to the test case in a separate browser tab simultaneously with test execution in the primary tab. Regards Jim Tue, 13 Sep 2016 14:27:18 -04002016-09-13T14:27:18-04:00/Support/Forum/spiratest/issues-questions/1534.aspx#reply2752