Relationship Matrix for tests

[RedHead]

Hello!

I have model with interdependent UseCases and Requirements. I added some Tests (via Testing window) to UseCases.
How can I create Relationship Matrix between these UseCases and Tests without direct linking Test to UseCase? what link type i should choose in Relationship Matrix criteria block?
Thanks,
RH.





I have Enterprise Architect Corporate Edition.

[Paolo F Cantoni]

Hello!

I have model with interdependent UseCases and Requirements. I added some Tests (via Testing window) to UseCases.
How can I create Relationship Matrix between these UseCases and Tests without direct linking Test to UseCase? what link type i should choose in Relationship Matrix criteria block?
Thanks,
RH.

Hi RH (in my younger days I too had red hair - "Mahogany Copper' to be precise {don't ask how I know}  )

I couldn't resist responding...  And please take my response in the spirit of humour with which it's provided - it IS Friday here in Australia as I write).

As I  read what you wrote, it sounds like you're trying to create a "Clayton's" relationship between the Test and Use case.
(Background:  Here in Oz, there used to be a non-alcoholic drink called "Clayton's" reputedly designed to give you the flavour of a spirit such as whisky without the "kick".  Its advertising slogan was:  "Clayton's:  The drink you have when your not having a drink!".  Larrakins that we Aussies are, the term "Clayton's" came to mean a faux (or fake) version of something)

So it sounds like you're trying to create a relationship without creating a relationship.  

As they say out west in North Carolina:  "Cayn't be durn, sarn".

The relationship matrix is specifically designed to render the relationships that MUST exist in tabular form.

So I'm afraid you've been offered the Eric Morcombe gambit: "Get out of that without moving..."   (Eric was a famous English comedic genius - now sadly, deceased)

You'll have to create a relationship between the Test and Use case for it to appear in the Relationship matrix.  A simple dependency should do to start with.

I hope this doesn't offend, it wasn't meant to - it (as you can see) just struck me as "funny" - and I appear to be in a jovial mood today...

Paolo

[RedHead]

Actually the other problem is, that I CANT create link Use Case to Test. When I choose 'Select Target Type'= "Test" in Create Link window, there is no test records to choose.

[Paolo F Cantoni]

Actually the other problem is, that I CANT create link Use Case to Test. When I choose 'Select Target Type'= "Test" in Create Link window, there is no test records to choose.

Hi Redhead!

Not sure where in EA you are working.

If you create a UseCase and a TestCase (such as from the Custom diagram tool).  You can link them with either the diagram or the Relationship matrix and the other rendering will track it...

You ARE creating "TestCase" elements in EA are you not?  If not then that's possibly where the problem is.   TestCases are UseCases with stereotype "testcase" and are understood by EA as test cases.  If you open the properties page for the TestCase, you should see UseCase in the caption and testcase in the Stereotype field.

YMMVWF4M...

HTH,
Paolo

[Graham_Moir]

I think Mr Redhead is talking about the Testing Window (at least he mentioned that in his original message) where you can create tests that are directly associated with an element, i.e. don't exist independently.   In this case of course the matrix won't work.

[RoyC]

I think Graham is right. RedHead is creating tests in the Testing window, and these tests are the exclusive properties of the element currently selected in the diagram or Project Browser. You can copy tests between elements, but each test is internal to its parent element.

You can, however, indicate that the tests defined in one element are of relevance to other elements, by creating connectors from the 'other' elements to the one containing the tests. You would have to record in each element's Notes that 'the tests in element XYZ are significant to this element'. However, to make it rather more obvious, you can use a Test Case element as a single repository of the tests and many other things associated with the tests, and create connectors to that element from the other elements. That is what Paolo is referring to.

Note, though, you are still not creating any connection directly between a test and an external element. And to record the progress of an element through a test, you would still have to copy that test into that element. The Test Case is more of a central store of tests and testing information that you copy into other elements.

[Paolo F Cantoni]

Yes, I see that this is what Redhead is doing.  It's just that I gave away the idea of requirements and tests being "internal" to an item, years ago - so I'm not familiar with that EA functionality.

In my experience the only tests that could/should? be"internal" to an item are so-called unit tests (at the level of the item).

Similarly with internal "requirements" - which EA is schizophrenic about.  I reserve those for "responsibilities" of the item.  Which are effectively unidirectional.

All others are external - you need to be able to make many-to-many relationships as Roy has suggested.  And...  Since making a test internal is making an implicit relationship between the item and the test, you might as well make it explicit an be able to track it better.

HTH,
Paolo