Test Details Dialog does not seem to work properly

[Christian Prison]

Hi,

I am trying to edit test cases (acceptance tests) by updating their status and putting some comments in the testing dialog (the one that opens on Alt+3), but my changes do not get applied (mainly because the save button in the testing view is deactivated).

I looked up in the helpfile, it says that I can also use the "Test Details Dialog" by doubleclicking on the test in the list, but that doesn't seem to work - neither for existing nor for new test cases!

Finally I found out that for requirements not set to "Validated", I can at least create and edit test cases with the "testing view (Alt+3)" whereas the "Test Details Dialog" still doesn't work.

Now I have the following questions:
1. Is anybody else facing similar problems?
2. Could the problems be related to the fact that I have created the requirements with the AddIn "RaQuest"?
3. If the behaviour is as expected (it's not a bug, it's a feature), then what is the concept for a tester to document his results if the respective requirement is set to "validated"?

I will download & install V7.1, maybe that helps. [...] I just did that - no change  

So I appreciate any reply!

Thanks & Best Regards,
Christian

[Dermot]

Hello Christian,

If the Requirement Element is "locked" the test dialog will also be locked.  So check that the other appliaction has not set this in locked mode,  by right-clicking the element and viewing the "LockElement" status in the context menu.

[Christian Prison]

Thanks, Dermot, for clarification.

As you can see from my original message, I had already considered this as one of the possible reasons ("Validated" is the locked status in my case). But in that case, my question No. 3 comes into picture:

What is the idea about locking a requirement? From my understanding, it is ment to identify that this requirement is now finalized and should not be changed anymore. If that is true, then the requirement would go into the implementation phase and finally, the tester would get it on his plate. He would look at the test cases and expect that he can set the values for the test like

a) the test has been run
b) it was run by this person
c) the result was passed, failed etc. as per the given combobox
d) some comments about what happened

But how can he do that if the test cases get locked along with the requirement?

Where am I making the mistake?

Thanks & Regards,
Christian

[Dermot]

Hello Christian,

When working strictly in EA: The Element.Status = "Valid" does not have any bearing on the "Lock" state of an Element.  If you are principly working with the third party product, then I would suggest you check in with RaQuest - this may be one the locking it.  Otherwise if you working prinicpaly in EA; simply set to: Off -  Lock Element (using the context menu - as stated above).