| Test Step | Expected Result
-- | -- | --
1 | Create an initial repository diagram.Click Button "Create a new Repository Model and Diagram from scratch" in menu bar. Follow the wizard (select project, specify file names) | The repository file are created in the project. The diagram is opened in an empty editor.
2 | Open the EMF tree editor of the generated repository model by clicking on the model file and selecting "Open With"->"Repository Model Editor". The tree editor can be used in the following steps to check whether changes in the diagram are also done in the underlying model. To do so, always perform a save after each change in the graphical editor and click into the tree editor (content is not refreshed if tree editor has no focus). | The tree editor is opened.
3 | Create a new Basic Component in the Repository Diagram Editor. Name it with a recognizable name.(I will refer to this component as "BC1".) | The Repository Diagram and Model contain a named Basic Component.
4 | Create a new Interface in the Repository Diagram Editor. Name it with a recognizable name.(I will refer to this component as "IP1".) | The Repository Diagram and Model contain a named Interface.
5 | Connect BC1 to IP1using a ProvidedRole. | An arrow shaped connector with a "<>" label appears between the Basic Component and Interface.
6 | Add a Signature to IP1. Name it with a recognizable name. (I will refer to it as "Sig1") | IP1 now contains a named Signature.
7 | Change the return type of Sig1 to bool (in the properties view). | The signature's label in the GMF Editor now displays "bool Sig1()".
8 | Delete BC1 by selecting it and then pressing the Del key. | BC1 and the Operation Provided Role pointing to IP1 disappear.
9 | Undo the deletion by pressing ctrl + z. | BC1 and the Operation Provided Role pointing to IP1 reappear.
10 | Delete IP1 by selecting it and then pressing the Del key. | IP1 and the Operation Provided Role pointing to it disappear.
11 | Undo the deletion by pressing ctrl + z. | IP1 and the Operation Provided Role pointing to it reappear.
12 | Add a SEFF to BC1. Select Sig1 as its Signature, when prompted to do so by a dialog. | BC1 contains a SEFF for Sig1.
13 | Double click the SEFF. The SEFF editor should open. Close it again. | The SEFF Editor displays and closes correctly.
14 | Add a Passive Resource to BC1's PassiveResourceCompartment. Name it with a recognizable name. | BC1 now contains a Passive Resource.
15 | Add a Component Parameter to the ComponentParameterCompartment. A Dialog for the name opens. Enter a recognizable name. | BC1 now contains a named Component Parameter.
16 | Add a Variable Characterisation to the Component Parameter. | The Component Parameter now contains a Variable Characterisation.
17 | Set a stochastic expression by clicking on the variable characterisation and writing the expression (e.g. a number). | The Variable Characterisation displays the stochastic expression.
18 | Add an InfrastructureInterface. Give it a recognizable name. (I will refer to it as "IP2") | The Repository Diagram and Model contain a named InfrastructureInterface.
19 | Connect BC1 to IP2 using an InfrastructureProvidedRole. | An arrow shaped connector with a "<>" label appears between the Basic Component and Interface.
20 | Create a new Basic Component in the Repository Diagram Editor. Name it with a recognizable name.(I will refer to this component as "BC2".) | The Repository Diagram and Model contain a second named Basic Component.
21 | Connect BC2 with IP1 using a RequiredRole. | An arrow shaped connector with a "<>" label appears between the Basic Component and Interface.
22 | Connect BC2 with IP2 using an InfrastructureRequiredRole. | An arrow shaped connector with a "<>" label appears between the Basic Component and Interface.
Beschreibung
Umgebung
Test Case Description