Bladeren bron

Merge pull request #1525 from Yakindu/test_fixes

Manual tests reviewed and improved.
Rainer Klute 8 jaren geleden
bovenliggende
commit
cef347e03e
16 gewijzigde bestanden met toevoegingen van 138 en 167 verwijderingen
  1. 4 4
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_00_installation.textile
  2. 1 1
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_01_update.textile
  3. 26 26
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_02_editor.textile
  4. 6 7
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_03_simulation.textile
  5. 3 4
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_04_help_integration.textile
  6. 5 4
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_05_validation.textile
  7. 6 7
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_06_expression_language_proposals.textile
  8. 12 13
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_07_custom_generators.textile
  9. 14 20
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_08_genmodel.textile
  10. 11 15
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_09_template_proposals.textile
  11. 8 10
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_11_operations.textile
  12. 19 22
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_12_refactor.textile
  13. 4 8
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_13_state.textile
  14. 8 10
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_14_example_wizard.textile
  15. 7 10
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_15_performance.textile
  16. 4 6
      manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_16_error_report.textile

File diff suppressed because it is too large
+ 4 - 4
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_00_installation.textile


File diff suppressed because it is too large
+ 1 - 1
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_01_update.textile


File diff suppressed because it is too large
+ 26 - 26
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_02_editor.textile


File diff suppressed because it is too large
+ 6 - 7
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_03_simulation.textile


+ 3 - 4
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_04_help_integration.textile

@@ -1,7 +1,6 @@
-h1(#Test2). Yakindu SCT Testcase 04 - Help Integration
-
+h1. YAKINDU Statechart Tools – 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.1 | Open documentation | <ol><li><p>Click on *Help → Help Contents*.</p></li><li><p>Expand entry _YAKINDU Statechart Tools Documentation_.</p></li></ol> | <p>Top-level entry _YAKINDU Statechart Tools Documentation_ is available.</p><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% |

+ 5 - 4
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_05_validation.textile

@@ -1,11 +1,12 @@
-h1(#Test2). Yakindu SCT Testcase 05 - Validation
+h1. YAKINDU Statechart Tools – Testcase 05 - Validation
 
 
 |_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
+| 5.0 | Test models | Import the project located on _manual-tests/org.yakindu.sct.test.manual_ in your source code repository into your workspace. | The test models needed below are available. | %{color:red}open% |
 | 5.1 | Expression error check | Open statechart ExpressionError01.sct | There are two error markers with the following error message:<p>"entry and 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.2 | Expression error check | Open statechart ExpressionError03.sct | There is one error marker at the definition 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 definition 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 definition 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% |

File diff suppressed because it is too large
+ 6 - 7
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_06_expression_language_proposals.textile


File diff suppressed because it is too large
+ 12 - 13
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_07_custom_generators.textile


File diff suppressed because it is too large
+ 14 - 20
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_08_genmodel.textile


File diff suppressed because it is too large
+ 11 - 15
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_09_template_proposals.textile


File diff suppressed because it is too large
+ 8 - 10
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_11_operations.textile


File diff suppressed because it is too large
+ 19 - 22
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_12_refactor.textile


+ 4 - 8
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_13_state.textile

@@ -1,10 +1,6 @@
-h1(#Test2). Yakindu SCT Testcase 13 - Smart Editing
+h1. YAKINDU Statechart Tools – Testcase 13 - Smart Editing
 
 |_. 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% |
-
-
-
-
+| 13.1 | State templates available | <ol><li><p>Select a state.</p></li><li><p>Press @[Ctrl+Space]@.</p></li></ol> | <ul><li><p>The following proposals are shown: "@Add subregion@", "@Add outgoing state@".</p></li><li><p>For each selected proposal, a corresponding documentation popup window opens.</p></li></ul> | %{color:red}open% |
+| 13.2 | Add composite behaviour | Double-click on the _Add subregion_ proposal. | A subregion is added to the selected state, containing an entry, a transition and a substate. The state is enlarged so that the whole content is shown. | %{color:red}open% |
+| 9.1 | Add orthogonal behavior | Double-click on the _Add outgoing state_ proposal. | A new state is added. A transition is drawn from the selected state to the new state. | %{color:red}open% |

File diff suppressed because it is too large
+ 8 - 10
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_14_example_wizard.textile


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

@@ -1,12 +1,9 @@
-h1(#Test2). Yakindu SCT Testcase 14 - Performance
+h1. YAKINDU Statechart Tools – Testcase 15 - Performance
 
 |_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
-| 15.1 | load model | Open statechart big_file.sct | new Statechart is in your Project inserted | %{color:red}open% |
-| 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? | %{color:red}open% |
-| 15.3 | performance check | save the Statechart | It shouldn't need a long time | %{color:red}open% |
-| 15.4 | change preferences | Window->Preferences->YAKINDU SCT->Diagram Appearance <p> disable "Enable live validation" | | %{color:red}open% |
-| 15.5 | performance check |  add a new state in your statechart | There is no error marker at the state | %{color:red}open% |
-| 15.6 | performance check | save the Statechart | It shouldn't need a long time. Error marker appears at the state | %{color:red}open% |
-
-
-
+| 15.1 | Loading big model | Open statechart _big_file.sct_. | The statechart is opened. | %{color:red}open% |
+| 15.2 | Performance check: editing | Add a new state to the statechart. | <ul><li><p>The editor works smoothly.</p></li><li><p>The validation is done quickly.</p></li><li><p>The overall user experience is okay.</p></li></ul> | %{color:red}open% |
+| 15.3 | Performance check: saving | Save the statechart. | <ul><li><p>Saving the statechart to a file is done quickly.</p></li></ul> | %{color:red}open% |
+| 15.4 | Changing preferences | <ol><li><p>In the main menu, select _Window → Preferences_.</p></li><li><p>Select _YAKINDU SCT → Diagram Appearance_.</p></li><li><p>Disable _Enable live validation_.</p></li></ol> | <ul><li><p>No error occurred.</p></li></ul> | %{color:red}open% |
+| 15.5 | Performance check | Add a new state to the statechart. | <ul><li><p>The new state has no error marker.</p></li></ul> | %{color:red}open% |
+| 15.6 | Performance check | Save the statechart. | <ul><li><p>Saving the statechart to a file is done quickly.</p></li><li><p>The new state from T15.5 has an error marker now.</p></li></ul> | %{color:red}open% |

+ 4 - 6
manual-tests/org.yakindu.sct.test.manual/testcases/sct_testcase_16_error_report.textile

@@ -1,11 +1,9 @@
-h1(#Test2). Yakindu SCT Testcase 16 - Error Report
+h1. YAKINDU Statechart Tools – Testcase 16 - Error Report
 
 |_. Nr |_. Testname |_. Test Instructions |_. Postconditions |_. Status|
-| 16.1 | trigger error  | open the SC Modeling view <p> Press *"Ctrl + Alt + l"* | in the left down corner should appear an error dialog | %{color:red}open% |
-| 16.2 | check error settings | Hit *enable* at the dialog <p> Press Next | A window opens <p> on the second site YAKINDU should listed <br> The hook behind YAKINDU should be set | %{color:red}open% |
-| 16.3 | check privacy policy | Press *configure* -> *privacy policy* | the browser should open and link you to the itemis AGB site | %{color:red}open% |
+| 16.1 | Triggering error | <ol><li><p>Open the _SC Modeling_ perspective.</p></li><li><p>Press @[Ctrl+Alt+L]@.</p></li></ol> | <ul><li><p>An error dialog is shown in the lower-left corner.</p></li></ul> | %{color:red}open% |
+| 16.2 | Checking error settings | <ol><li><p>In the dialog, check _enable_.</p></li><li><p>Press _Next_.</p></li></ol> | <ul><li><p>A window opens.</p></li><li><p>On the second site (???) YAKINDU should listed.</p></li><li><p>The check mark behind YAKINDU should be set.</p></li></ul> | %{color:red}open% |
+| 16.3 | Checking privacy policy | Press *configure* -> *privacy policy* | the browser should open and link you to the itemis AGB site | %{color:red}open% |
 | 16.4 | Error selected | Press *enable* -> *enable* | Dialog window appears. Problem looged in ... | %{color:red}open% |
 | 16.5 | Check the error | Press *deatils* | There should be an *Strack Trace* shown in a window | %{color:red}open% |
 | 16.6 | Error sended | Cklick on *send* | "Thank you" dialog appears | %{color:red}open% |
-
-