Crazy Test Engineers

[Zidane]

Hi All!

In the meantime I am not doing EA evaluation for my group only, but I am something like a Sparx representative in my company.

Now test engineers are asking if there is a one to many relationship possible between a test case and model elements...
and, if yes... if creator of the test case gets informed somehow about changes in one of the related elements.

For me the request makes absolutely sense. They want to connect a test case with requirements, use cases, design and implementation elements and want to redo the test when one of the elements changes.

What I found out till now (please correct me if I'm wrong)

*) Test Case is related to one model element only (can be a package of course)

*) There is no notification if that element changes

*) There is no view of all testcases within a package or the whole model

*) If I am not totally wrong the "Import element scenario(s)" is buggy in v6.5.796
 
Any suggestions how I could satisfy my testers needs with Enterprise Architect?

Best regards,
DD  

[Jan ´Bary´ Glas]

1) Internal Test Case is connected to one lement only. External is an element, so is you may link wherever you want. You get external Test Case as steretypeds Use Case (stereotype is "testcase").
2) No auto-notification that I know exists, but you may see in Hierarchy panel all related elements for any testcase.
3) If you have external TestCases you may try Advanced search
4) Lasd tries in 792 and it worked properly for both scenarios and constraints.

I hope this may push you forward.

[Zidane]

Thank you so much. You are a BIG help  

ad 3) I have a good feeling THAT and a rough idea HOW it would work with a Custom SQL Search. Nevertheless if Advanced Search/Search In would support Hierarchy next to Entire Model and Current Tree Selection, this would be much easier.

Best regards,
DD

[Jan ´Bary´ Glas]

Thank you so much. You are a BIG help  

ad 3) ... if Advanced Search/Search In would support Hierarchy ...

DD

I use tracebility throughout the model. Everything is somehow conected to everything. That means searching in Hierarchy is the as searching the entire model. (Of course there may be "number of levels parameter").

[mikewhit]

Some time back I put in a request that Test be given another look in terms of EA features - in principle, every model element needs a test or some kind of verification (think V model).

Since it's so pervasive, it really needs another layer (think Photoshop) or means of visualisation so that diagrams don't get cluttered with dozens of tests appearing with the model elements.

Also you need to be able to demonstrate that every element (and package) has its corresponding verification element.

But you could also make a similar case in respect of Requirements ... and obviously each test should probably refer to a requirement.

In this ideal system, you would have traceability to requirements and verification for all aspects of your model.

Ever the optimist ...