| || |
Req Coverage From Test Case vs Test Set Test Inst
When a test case is linked to a requirement in the Test Plan, and then added to a test set , when you look at the test instance the Test coverage does not show.
Create a requirement
Create a test case
Link req to test case in test Plan
create a test set in test lab
add the test case to the test set
Double click on the test to se the test instance
Look at the linkage and coverage and look at the Requirement coverage tab.
Link is not there
If you look at the requirement coverage in the Test plan for hat test case it is linked to the requirement.
I have Looked into the Help file and validated that we have:
I would assume hat the test instance coverage would also show the test case link to the req. Could this be causing this not to sync?
Also by default is this option set to "Y" during install?
I also need to better understand the difference of linking from test case to req vs Linking test instance to req.
ALLOW_REQ_COVERAGE_BY_TEST_INSTANCE (Set to Y)
Help File text:
This parameter determines whether the option to create coverage between requirements and test instances is available.
If the parameter does not exist, is empty, or is set to "N", then this option is unavailable. If the parameter is set to "Y", you can create and view coverage between requirements and test instances from the following locations:
In the Requirements module, in the Requirement Details view, in the Test Coverage tab
In the Test Plan module, in the Test Instance Properties dialog box, in the Linkage and Coverage view
Re: Req Coverage From Test Case vs Test Set Test Inst
The 2 types of coverage are different. Instance coverage has to be done for each instance. Plan coverage is done once in the plan. So plan coverage wont show with instance coverage in the Lab.
Coverage by instance seems a lot of work and comes a bit late in the testing process. I would put the site parameter to N unless there is a specific need for instance coverage; a test that covers a requirement "should" do so irrespective of the campaign it runs in. If a test is re-used for different requirements it may be easier to duplicate it (or set up calling tests in the plan). And using cycles is normally good enough for tracking coverage by campaign - my 2c