changes.mady.by.user Unknown User (lfir)
Saved on Aug 07, 2020
changes.mady.by.user Unknown User (tdda)
Saved on Sep 03, 2020
Let's start by creating a Test Execution from a Test Plan from the context
menu.
Main information is already copied to the create a Test Plan
Image Modified
After Test Execution creation we can access to the issue and visualize it.
From the Test Execution we will now select "Execute."
And we will proceed with the test.
We have marked all of the steps has PASS have PASSED and in result the Test is also marked as PASS.
Looking to the Test Execution
, as expected it shows the result of the associated Test Runs and they appear
as PASS
.
Looking to the Test Plan has expected it shows the result of the associated Test Execution and they appear
as failed
Looking to the Test
We can see :
We can now see a change in the Requirement Status it has moved from NOK to OK.
We also have the possibility of evaluating the executions and state of the Requirement against Scope, Version or Environemnt.
Image Added
In this case for example we evaluate the state of the Requirement against Version 3.0
And the results as you can see is "TODO" as we didn't run any test execution against that version, we only ran it against version 1.0.
If you are curious about the overall requirement status that value reflects the configuration of the app in your instance.
In this case
You can ask you administrator to change to any other option that better goes with your requirements.
