![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: determining overall pass/fail/untested Topic Summary: Created On: 18-Apr-2007 20:03 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Oh boy. This turned out to be embarrassingly easy. I was worried about performing this logic inside the loop. What I needed to do was perform the logic OUTSIDE the function call, which operates not on the entire module (so to speak) but just on a single object. I sometimes lose that perspective. Anyway, I set up global booleans for each test result I was looking for -- itsPass, itsFail, itsUntested -- with a default value of false. Then I trip the appropriate variable to true when I examine the value at the destination links. Then, after the entire function has been called, I set a string based on a priority conditional scheme of my booleans. Wow. That was easy. Thanks again for chiming it! <> David | |
![]() |
|
I'm trying to gather together test statuses. I've got a system specification, with child specs that have their own test case modules and test procedure modules. My pass/fail/untested attribute exists in that procedure module (3 levels below the system spec). I've been able to see the status value for each low-level procedure (in layout DXL) but haven't figured out how to create a column that performs logic on those values (untested crushes fail, fail crushes pass) showing just one value representing the combined status of all the values.
I've been doing all this work with the analysis wizard, which seems to generate a function that ends up calling itself within itself depending on depth. Haven't wrapped my head around where the logic should sit. Any suggestions? Thanks. <> David |
|
![]() |
|
![]() |
|
Is this a logic problem (you don't understand the algorithm) or an access problem (you cannot see the data in modules a few links away)?
A possible logic solution is attached. - Louie |
|
![]() |
|
![]() |
|
It's definitely not an access problem -- I can see the values I want to process. And I haven't dug into the logic quite yet -- I'm assuming that won't be a big problem. My confusion is where to place the logic in the code generated by the analysis wizard. It defines a function called "showIn". Within that function there is an evaluation of depth. If it's one level, the attribute is displayed, if it's at another level the function calls itself.
For example, I could have a single system requirement that has 5 test procedures located 3 levels below. I can see those 5 results. My problem is converting those 5 results into a single result in a new column. Maybe I'm approaching this wrong? For instance, in Excel, one would just create a formula to operate on the cells and make the determination. Thanks for the reply. It seems like this won't be too difficult once I get the breakthrough concept. <> David |
|
![]() |
|
![]() |
|
I'm not looking at the wizard's code but seem to recall some of it. Try this:
At the top define and create a Buffer. Inside the recursive function at the point you have the data you wish to 'display', instead of 'display' add that to the buffer; be sure to add the "\n" at the end. After the call to the recursive function, 'display' the contents of the buffer. If you figure to do clever calculations, then instead of a Buffer you can use a Skip list; perhaps using either the test case ID as the 'key' or perhaps using a global integer that's incremented each time you insert into the Skip. After the recursions plow through the Skip doing you calculations. - Louie |
|
![]() |
|
![]() |
|
Buffer, eh? That sounds like a step in the right direction. This newbie will have to spend a bit more time with the manual. Thanks!
<> David |
|
![]() |
|
![]() |
|
Oh boy. This turned out to be embarrassingly easy. I was worried about performing this logic inside the loop. What I needed to do was perform the logic OUTSIDE the function call, which operates not on the entire module (so to speak) but just on a single object. I sometimes lose that perspective.
Anyway, I set up global booleans for each test result I was looking for -- itsPass, itsFail, itsUntested -- with a default value of false. Then I trip the appropriate variable to true when I examine the value at the destination links. Then, after the entire function has been called, I set a string based on a priority conditional scheme of my booleans. Wow. That was easy. Thanks again for chiming it! <> David |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
determining overall pass/fail/untested
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.