Add Test Cases

[Christy Bailey]

  I'm a new user to EA and have had no training.  I'm trying to set up a new test case and everything in the test case list is disabled.  Do I need to enable Security in order to be able to use the test functionality or what am I doing wrong?  I've gone through the online help and cannot find anything about troubleshooting.  Any assistance is greatly appreciated.

[KP]

Test cases are owned by elements, so you need to first
select an element in either the Project View or on a diagram and the commands on the Test Cases context menu should be available.

HTH

[Paolo F Cantoni]

Test cases are owned by elements, so you need to first
select an element in either the Project View or on a diagram and the commands on the Test Cases context menu should be available.

HTH

There are two kinds of Test Cases! - those that are internal to elements (and can't be promoted AND won't appear in the Relationship Matrix) and those created by dragging from the Toolbox - which I have just noticed are really UseCases with the stereotype «testcase»!  These latter Test Cases WILL appear in the Relationship Matrix as Test Cases, but NOT as UseCases.

Consistency, Consistency, Consistency! ^TM

Orthogonality, Orthogonality, Orthogonality! ^TM

Paolo

BTW: Don't forget you have to Right-Click to add a new internal Test Case!

[mikewhit]

AND won't appear in the Relationship Matrix

... and hence are no use for test/requirements coverage purposes ...


PS. shouldn't those three "Orthogonality"s be at right angles to each other ?

[Paolo F Cantoni]

PS. shouldn't those three "Orthogonality"s be at right angles to each other ?

Yes!!!  Assume the third one is coming out of the screen at you!

Orthogonally (and Consistently)
Paolo

[thomaskilian]

Since we all use a 4-dimensional system, where is the 4th?

I (now) started to go into depth with testing. Maybe I have to get more familiar with that, but obviously there is very limited support for generating test suites. That is: no possibility to bundle a set of test cases and make it a suite. I thought it could be helpful if the Model Document mechanism could be used: place all elements with test scenarios in such a class and create the documentation. For the time being it seems that I have to write some scripts to support me.

Also I was wondering why the different test types are bundled for each element. According to Sparx own documentation unit tests apply to classes (etc.), system tests to business needs (that is Use Cases), a.s.o. So I would not expect all types to appear for all elements. Any thoughts?

[mikewhit]

Requirements and Tests both need to be 'linkable' to any other EA element, so that you can express requirements and test coverage in each direction.

But you don't want them cluttering up every diagram, which is why I earlier observed that a separate diagram layer might be a way to show them when necessary.

The 'internal' test cases are no use in this respect.

The only alternative (that I haven't tried) would be to place a group (suite) of tests as 'internal' test cases to a Test Case stereotype, and then link that as required to the class(es), requirements, etc.

But in order not to have the diagrams filled up with test cases, you have to do the linking using the Relationship Matrix, not the most user-friendly way of doing what should after all be a GUI operation for simplicity.

Do I sound frustrated ?

[voice of Marvin] EA Test cases ... don't talk to me about EA Test cases ...

[thomaskilian]

That door again...

It seems I have to start with scripting