Question & Answer
Question
When you create test architecture using Directed association relation, you get test architecture which contains test component of block A, B,C and also dummy driver. However, when you create test architecture using association relation, you get test architecture which contains only test component of block A,B,C.
When you create test architecture using any other relation, say composition or aggregation, you get test architecture which contains only the dummy driver.
Also, when you use harmony profile then using Directed association and association also, you get only the dummy driver.
When you create test architecture using any other relation, say composition or aggregation, you get test architecture which contains only the dummy driver.
Also, when you use harmony profile then using Directed association and association also, you get only the dummy driver.
Why is this happening?
Answer
The rules for the creation of test components are explained in the TestConductor user guide (TestConductor_User_Guide.pdf in Doc/pdf_docs), there is a section TestArchitectures -sub section SUT and TestComponents.
In short: If there is no test component which can send stimuli to the SUT then a dummy driver is created. Otherwise it is not needed and not created.
For aggregation kind "composition" no test component is created - according to UML specification, a composite is treated as internal part of the SUT which shouldn't be stubbed.
For aggregation kind "shared" no test component is created - for a shared association TestConductor cannot know who is responsible for instantiating the shared element.
For Harmony projects associations are ignored. Here TestConductor assumes interfaces are modelled using ports and associations are not relevant.
For aggregation kind "composition" no test component is created - according to UML specification, a composite is treated as internal part of the SUT which shouldn't be stubbed.
For aggregation kind "shared" no test component is created - for a shared association TestConductor cannot know who is responsible for instantiating the shared element.
For Harmony projects associations are ignored. Here TestConductor assumes interfaces are modelled using ports and associations are not relevant.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSB2MU","label":"IBM Engineering Systems Design Rhapsody"},"Component":"Test Conductor","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.4","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Product Synonym
Rational Rhapsody
Was this topic helpful?
Document Information
Modified date:
27 May 2022
UID
ibm16115810