![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Action/Results columns for Test Cases? Topic Summary: Created On: 24-May-2008 00:04 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I'm planning to use DOORS to record and mantain our Test Cases. One popular structure in other systems is to have separate columns for "Actions" and "Expected Results."
I could create two text attributes in DOORS but I'm worried that I will lose all the built in functionality associated with the singular Object Text field. The other option we've discussed is creating an Action/Result Attribute. The information all goes into the Object Text but we can use the A/R flag to change how the Action vs Results sections are 'printed' or made visible in various views. Has anyone wrestled with a similar problem? Found any good answers? Thanks, Larry Fast |
|
![]() |
|
![]() |
|
I made a presentation at the german user conference in 2006, where I explained how we analysed the information model of test specifications and how we implemented it in DOORS. You might see the presentation at http://www.telelogic.de/campai...act_popup.cfm?ID=4585
(If you have problems accessing it, tell me and I would send it to you per Email). We store the test results in another DOORS module (to separate life cycle of the documents). There is also a presentation on this :-) that I held on the ReConf in München this year ; see http://2008.reconf.de/fileadmi...g_Draeger_Medical.pdf Maybe this would help you find answers to your questions. Do not hesitate to ask more if you need. |
|
![]() |
|
![]() |
|
Larry
We use a modified version of the Test Tracking Toolkit. The test procedure module has the test actions in the Object Text structured in a hierarchical manner and an additional attribute for Expected Observations/Comments. Essentially one main view for setting up the actions and expected results and one view for entering the test results. So in our situation, all the test information is in one module - We then use WEXP to extract the various components using different views. The test report is pretty much an automatic production and saves many man hours of work. email me if you would like further information. ------------------------------ Gordon Woods BAE Systems gordon.woods2@baesystems.com |
|
![]() |
|
![]() |
|
Thanks Emmanuel,
We just develop software so our test environment is much simpler. But the system you presented has filled my head with ideas. I'm still new to DOORS but I will look back at your presentation for inspiration as we move forward. Cheers, Larry Fast |
|
![]() |
|
![]() |
|
Thanks Gordon,
It sounds like my concerns about working with an extra Text attribute are unfounded. We don't currently plan to use Test Tracking for our test cases but I modified our Attributes to align with the Test Tracking model of the world. If we change our minds later we won't be locked out. Cheers, Larry Fast |
|
![]() |
Telelogic DOORS
» General Discussion
»
Action/Results columns for Test Cases?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.