Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Qu... > Test Cases - Blue Lines, ...
Had a few general questions regarding Test Cases/Individual Test Runs.
1. When executing a Test Case for a new Release, we may encounter a step that needs to be updated to reflect new functionality (that wasn't caught ahead of time). Is there a way to make that update while executing the run so that it would be documented and update the Test Case going forward?
2. Is there a way to insert a row within a Test Case that isn't necessarily a step, but more for informational purposes for upcoming steps (i.e "The following steps are time critical") that doesn't require you to technically Pass/Fail/Block it as a "Step":
Step 1.
Action #1
Result #1
**General Note (Time Sensitive Step)**
Step 2.
Action #2
Result #2
3. I created a Custom Test Step property for Requirements where specific steps list the Req # they are associated with. Is there a way to turn that Req # into a link to the Requirement that is also in Spira? It seems like the Requirement ID assigned to that Requirement by Spira can be linked somehow, but I cannot get it work properly.
Thank you!
Hello,
Thank you for interesting questions!
1. Updating a Test Step during execution - No, this is not currently possible.The Best Practice / Workaround: To document the issue for the current run and fix it for the future, the tester would need to open up another browser tab, open up the underlying test case and edit the steps there. Then you can re-execute the test with the changes.
Spira does not let you edit the test cases during execution since when you start a Test Run in Spira, the system takes a "snapshot" of the Test Case at that exact moment. This is done so that the historical record of the execution doesn't change, even if someone alters the original Test Case later.
However, with Exploratory Testing you can add/clone, rearrange or remove steps as needed.Check here for more details: https://spiradoc.inflectra.com/Spira-User-Manual/Test-Execution/#exploratory-test-execution
2. Inserting an "Informational Only" row in a Test Case - Technically, no.Spira requires every row designated as a "Step" to have an execution status (Pass, Fail, Blocked, etc.) when the test is run. There is no native "Info Only" row type that skips the status requirement.
The Best Practice / Workaround: Instead of trying to force a separate row, we highly recommend adding the informational note directly to the Description / Action field of the step it applies to. Because those fields support Rich Text, you can format the note to stand out clearly.
3. Turning a Requirement ID into a clickable link in a Custom Field - There is no way to do this automatically. What you can is to manually add a link to the artifact token by copying it from the browser URL.Please note that the custom property type 'text' should have a Rich Text option turned on.
Regards,Victoria -
And if you have any questions, please email or call us at +1 (202) 558-6885
