Merge pull request #717 from Yakindu/Testplan_to_textile

Testplan to textile

manual-tests/org.yakindu.sct.test.manual/tectcases/Yakindu_SCT_Testcase_04_-_Help_Integration.textile

@@ -0,0 +1,7 @@
+h1(#Test2). Yakindu SCT Testcase 04 - Help Integration
+
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 4.1 | Open Help Documentation | Click on *Help→Help Contents.*<p>Open YAKINDU Statechart Tools.</p> | Top-level entry YAKINDU Statechart Tools is available.<p>Subordinate entries are shown.</p> | %{color:red}open% |
+| 4.2 | Welcome page | Click on *Help→Welcome.* | The YAKINDU Statechart Tools welcome page is shown. | %{color:red}open% |
+| 4.3 | Links on welcome page | Click on each link on the welcome page. | Check whether each link a) works and b) points to what the link text implies. | %{color:red}open% |

manual-tests/org.yakindu.sct.test.manual/tectcases/Yakindu_SCT_Testcase_05_-_Validation.textile

@@ -0,0 +1,14 @@
+h1(#Test2). Yakindu SCT Testcase 05 - Validation
+
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 5.1 | Expression error check | Open statechart ExpressionError01.sct | There is four error markers with the following error message:<p>"entry, exit, events are allowed as local reactions only."</p> | %{color:red}open% |
+| 5.2 | Expression error check | Open statechart ExpressionError03.sct | There is one error marker at the specification section with the following error message:<p>"In/Out declarations are not allowed in internal scope."</p> | %{color:red}open% |
+| 5.3 | Expression error check | Open statechart ExpressionError04.sct | There is one error marker at the specification section with the following error message:<p>"Local declarations are not allowed in interface scope."</p> | %{color:red}open% |
+| 5.4 | Expression error check | Open statechart ExpressionError05.sct | There is one error marker at the specification section with the following error message:<p>"Only one default/unnamed interface is allowed."</p> | %{color:red}open% |
+| 5.5 | Statechart error check | Open statechart StatechartError01.sct | There is one error marker at the state with the following error message:<p>"A state must have a name."</p> | %{color:red}open% |
+| 5.6 | Statechart error check | Open statechart StatechartError02.sct | There is one error marker on the transition with the following error message:<p>"Outgoing Transitions from Entries can not have a Trigger or Guard."</p> | %{color:red}open% |
+| 5.7 | Statechart error check | Open statechart StatechartError03.sct | There is one error marker on each of the states with the following error message:<p>"Duplicate SpecificationElement 'A' in Region 'main region'"</p> | %{color:red}open% |
+| 5.8 | Statechart error check | Open statechart StatechartError04.sct | There is one error marker on state 'B' with the following error message:<p>"Node is not reachable."</p> | %{color:red}open% |
+| 5.9 | Statechart error check | Open statechart StatechartError05.sct | There is one error marker on the entry node with the following error message:<p>"Entries must not have more than one outgoing transition."</p> | %{color:red}open% |
+| 5.10 | Statechart error check | Open statechart StatechartError06.sct | There is one error marker on the choice with the following error message:<p>"A choice must have at least one outgoing transition."</p><p>There is a warning maker on the choice with the following warning message:</p><p>“Missing trigger. Transition is never taken. Use 'oncycle' or 'always' instead."</p> | %{color:red}open% |

manual-tests/org.yakindu.sct.test.manual/tectcases/Yakindu_SCT_Testcase_06_-_Expression_Language_Proposals.textile

@@ -0,0 +1,12 @@
+h1(#Test2). Yakindu SCT Testcase 06 - Expression Language Proposals
+
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 6.1 | Extend statechart interface | Replace the statechart specification by the following:<p>&emsp;@namespace Staircase@</p><p>&emsp;@internal:@<br>&emsp;@var light : boolean@</p><p>&emsp;@interface A:@<br>&emsp;@in event keypress@</p><p>&emsp;@interface B:@<br>&emsp;@in event keypress@</p><p>Select transition with keypress trigger and double-click on trigger.</p><p>Replace "keypress" by "A.keypress" to qualify the event.</p> | No error messages are shown. | %{color:red}open% |
+| 6.2 | Create another statechart | Create a new statechart model and name it OtherStatechart.<p>Replace the default text in the definition section by the following:</p><p>&emsp;@namespace OtherStatechart@</p><p>&emsp;@interface A:@<br>&emsp;@out event e1@<br>&emsp;@in event e2@</p><p>&emsp;@interface B:@<br>&emsp;@out event e1@<br>&emsp;@in event e2@ | The new statechart OtherStatechart is created. It does not have any error markers. | %{color:red}open% |
+| 6.3 | Test state proposals | Select state LightOff.<p>Open properties view.</p><p>Place the cursor in front of the expression in the state specification and press *[Ctrl+Space]*.</p> | Only the following proposals should be displayed:<p>&emsp;- A<br>&emsp;- B<br>&emsp;- light<br>&emsp;- [<br>&emsp;- after<br>&emsp;- always<br>&emsp;- entry<br>&emsp;- every<br>&emsp;- exit<br>&emsp;- oncycle | %{color:red}open% |
+| 6.4 | Test transitions proposals | Select transition with trigger A.keypress.<p>Open properties view.</p><p>Move cursor in front of A.keypress and press *[Ctrl+Space]*.</p> | Only following proposals should be displayed:<p>&emsp;- A<br>&emsp;- B<br>&emsp;- #<br>&emsp;- /<br>&emsp;- [<br>&emsp;- after<br>&emsp;- always<br>&emsp;- default<br>&emsp;- else<br>&emsp;- every<br>&emsp;- oncycle| %{color:red}open% |
+| 6.5 | Test transitions proposals | Move cursor behind A.keypress and press *[Ctrl+Space]*. | Only following proposals should be displayed:<p>&emsp;- keypress<br>&emsp;- #<br>&emsp;- ,<br>&emsp;- .<br>&emsp;- /<br>&emsp;- [ | %{color:red}open% |
+
+
+

manual-tests/org.yakindu.sct.test.manual/tectcases/Yakindu_SCT_Testcase_10_-_ExampleFiles.textile

@@ -0,0 +1,5 @@
+h1(#Test2). Yakindu SCT Testcase 09 - Templateproposals
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 10.1 | Create Example File | Select *File → New → Example…*.<p>Select *YAKINDU SCT Example → Statechart Examples*.</p><p>Click *Next*.</p><p>Select traffic_light.</p><p>Click *Finish*.</p> | The Trafficlight example is created into the workspace  | %{color:red}open% |
+

manual-tests/org.yakindu.sct.test.manual/tectcases/Yakindu_SCT_Testcase_13_-_State.textile

@@ -0,0 +1,10 @@
+h1(#Test2). Yakindu SCT Testcase 13 - State
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 13.1 | State templates available | Select a state. Press *[Ctrl+Space]*. | The following proposals are shown in a drop-down menu:<p>&emsp;@Add subregion@</br>&emsp;@Add outgoing state@</p><p>For each keyword proposal a corresponding documentation popup window opens when the respective keyword is clicked.</p><p>A completion window should appear with the following entries:</p> | %{color:red}open% |
+| 13.2 | Add composite behaviour | Select Add *subregion*. | A subregion should be added to the selected state with an entry, a transition and a substate. The states bounds should enlarge so that the whole content is shown | %{color:red}open% |
+| 9.1 | Add orthogonal behavior | Select Add *outgoing state*. | A new state should be added. A transition should be drawn from the selected state to the new state. | %{color:red}open% |
+
+
+
+