Anyone willing to share how they are managing traceability of requirements in DOORS to Test Cases and the associated pass\fail\not run status of those Test Cases?
*Are you creating and managing Test Cases within DOORS?
*Are you using an electronic integration between DOORS and a Test Management tool? e.g. integration with IBM Quality Manager, HP Quality Centre\ALM, others
*Are you performing a manual integration of some sort? e.g. exporting requirements data from DOORS and importing into to a Test tool, or the other way around, or both?
*Some other lateral method?
Why do I ask? I have tried pretty much all combinations an permutations that I can think of to try and get requirements and test data into one tool to produce a consolidated RTM that allows you to produce sub RTM views such as a Verification Cross Reference Matrix (VCRM) that can report on the test coverage and test result status of requirements. It's getting harder to do this and interested in any new ideas.
Paul Miller,
Melbourne, Australia
SystemAdmin - Tue Aug 28 19:26:10 EDT 2012 |
|
Re: Managing Traceability to Test Cases and Test Results
DOORSWizard - Tue Aug 28 19:34:07 EDT 2012
We've found success with managing the test cases within DOORS. You lose out on the ability to automatically kick off a test but you can always export a procedure to excel, run it and import back into DOORS.
|
|
Re: Managing Traceability to Test Cases and Test Results
SystemAdmin - Mon Sep 03 07:00:20 EDT 2012 DOORSWizard - Tue Aug 28 19:34:07 EDT 2012
We've found success with managing the test cases within DOORS. You lose out on the ability to automatically kick off a test but you can always export a procedure to excel, run it and import back into DOORS.
However, integrating DOORS with a test management tool makes the testers life easier and using DOORS for traceability makes reporting easier.
|
|
Re: Managing Traceability to Test Cases and Test Results
SystemAdmin - Mon Sep 03 16:54:12 EDT 2012 SystemAdmin - Mon Sep 03 07:00:20 EDT 2012
Separate your test cases from your test runs as well! For example one module for the test cases - linked to the requirements, and one or more modules for the test runs, linking the results of the test runs to the test cases. My experience is that that makes tracing and reporting easier.
However, integrating DOORS with a test management tool makes the testers life easier and using DOORS for traceability makes reporting easier.
Would you be able to identify which Test Management tool you are using and also the integration tool.
Of particular interest is whether the integration uses a point in time data synchronisation to copy requirements data from DOORS to the Test tool, and how do the testers know exactly what has changed to the copy of requirements data in the test tool? That is, what is new, what has been deleted an what has been modified.
Paul Miller,
Melbourne, Australia
|
|
Re: Managing Traceability to Test Cases and Test Results
SystemAdmin - Mon Sep 17 10:15:11 EDT 2012 SystemAdmin - Mon Sep 03 16:54:12 EDT 2012
sekrboe wrote: "....integrating DOORS with a test management tool makes the testers life easier...."
Would you be able to identify which Test Management tool you are using and also the integration tool.
Of particular interest is whether the integration uses a point in time data synchronisation to copy requirements data from DOORS to the Test tool, and how do the testers know exactly what has changed to the copy of requirements data in the test tool? That is, what is new, what has been deleted an what has been modified.
Paul Miller,
Melbourne, Australia
Then there is the DOORS to RQM integration. Before DOORS 9.4 this was also a copying of information. However, from 9.4 the integration uses OSLC and there is no copying of information between the systems...
|
|
Re: Managing Traceability to Test Cases and Test Results
Mark_Gray - Tue Feb 11 14:48:16 EST 2014 SystemAdmin - Mon Sep 17 10:15:11 EDT 2012
I've used the DOORS HP QC integration, which does copy the requirements to HP QC and other attributes as well. For the attributes you can decide on who is the owner, DOORS or HP QC. The synchronization is either on a timer or manually triggered. In QC you get information about the change to requirements, if there is a change... Some years ago now that I looked at it.
Then there is the DOORS to RQM integration. Before DOORS 9.4 this was also a copying of information. However, from 9.4 the integration uses OSLC and there is no copying of information between the systems...
Have setup an integration between DOORS 9.3 and RQM 4.0.0 using the RQM Interface as a sync between both systems. The ability to push rqmts from DOORS to RQM works, but is VERY Limited in what is pushed over. the DOORS RQM interface only copies over the Module, Absolute Number, and Object Text.
With this DOORS to RQM interface, there isn't any ability to identify or configure they integration to copy over any other attributes like Requirement ID, Verification Method, Pass/Fail, or any other useful DOORS attribute.
|
|