Merge pull request #873 from Yakindu/improve_testplan

Improve testplan

manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_10_example_files.textile

@@ -1,5 +0,0 @@
-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/testcases/sct_testcase_12_refactor.textile

@@ -9,7 +9,7 @@ h1(#Test2). Yakindu SCT Testcase 12 - Refactor
 | 12.2.3 | Simulate | Run simulation. | The behavior of the refactored model is equivalent to its behavior before refactoring. The state *LightSwitch* state is highlighted in red. Transitions between *LightOff* and *LightOn* can be observed in the new editor tab mentioned in T12.2. | %{color:red}open% |
 | 12.3 | Inline subdiagram | Select the *LightSwitch* state.<p>Right click, then select *Refactor → Inline Subdiagram*.</p> | See T12.1. | %{color:red}open% |
 | 12.3.1 | Simulate | Run simulation | Behavior should be the same as before re-factoring | %{color:red}open% |
-| 12.4 | Prepare statechart | - Delete the transition from LightOn to LightOff and the state behavior of both states <p>- make a new transition from LightOff to LigtOn <p>- Enter event keypress/light = true as trigger and action for both transitions  | A new transition with trigger and action keypress/light = true is created. The other transition has keypress/light = true as trigger and action | %{color:red}open% |
+| 12.4 | Prepare statechart | - Delete the transition from LightOn to LightOff and the state behavior of both states <p>- make a new transition from LightOff to LigtOn <p>- Enter event A.keypress/light = true as trigger and action for both transitions  | A new transition with trigger and action keypress/light = true is created. The other transition has keypress/light = true as trigger and action | %{color:red}open% |
 | 12.5| Fold Incoming Actions | Select LightOn state  <p> Right click on the state <p> Select Refactoring -> Fold Incoming Actions | the action is shown in in the state LightOn and only the trigger is shown in the transitions  | %{color:red}open% |
 | 12.6| Unfold Entry Actions | Select LightOn state  <p> Right click on the state <p> Select Refactoring -> Unfold Entry Actions | the action is shown behind the trigger again | %{color:red}open% |
 | 12.7| Fold Outgoing Actions | Select LightOff state  <p> Right click on the state <p> Select Refactoring -> Fold Outgoing Actions | the action is shown in in the state LightOff and only the trigger is shown in the transitions  | %{color:red}open% |

manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_15_performance.textile

@@ -0,0 +1,12 @@
+h1(#Test2). Yakindu SCT Testcase 14 - Performance
+
+|_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 15.1 | load model | Open statechart big_file.sct | new Statechart is in your Project inserted | |
+| 15.2 | performance check | add a new state in your statechart | works the editor smooth? What does it feel like? How long it needs to validate? | |
+| 15.3 | performance check | save the Statechart | It shouldn't need a long time | |
+| 15.4 | change preferences | Window->Preferences->YAKINDU SCT->Diagram Appearance <p> disable "Enable live validation" | | |
+| 15.5 | performance check |  add a new state in your statechart | There is no error marker at the state  | |
+| 15.6 | performance check | save the Statechart | It shouldn't need a long time. Error marker appears at the state | |
+
+
+