| 41 | | * Comments from PLATFORM_STANDARDS_MANUAL_TESTS_R1 will be executed: |
| 42 | | * Test cases may contain clearly defined prerequisites - only one in between creating or opening a new book must be the chosen step in every test case. |
| 43 | | * All test cases must end with steps: "Save the book." and "Load the book." and in case needed - a last step to show that the changes made to the book are saved in it. |
| 44 | | * "When writing manual tests, do not forget the general guideline of the project: Work towards the goal!" will be revised as "When writing manual tests, keep in mind the general guideline of the project!". |
| 45 | | * Unnesesary highlights such as "Non-integer scores are STRONGLY disencouraged." will be changed to lowercase letters. |
| | 41 | Comments from PLATFORM_STANDARDS_MANUAL_TESTS will be executed: |
| | 42 | * Test cases may contain clearly defined prerequisites - only one in between creating or opening a new book must be the chosen step in every test case. |
| | 43 | * All test cases must end with steps: "Save the book." and "Load the book." and in case needed - a last step to show that the changes made to the book are saved in it. |
| | 44 | * "When writing manual tests, do not forget the general guideline of the project: Work towards the goal!" will be revised as "When writing manual tests, keep in mind the general guideline of the project!". |
| | 45 | * Unnesesary highlights such as "Non-integer scores are STRONGLY disencouraged." will be changed to lowercase letters. |
| | 46 | |
| | 47 | TestCases: |
| | 48 | * a link to Sophie2's Testlink will be added to the wiki page - http://sophie2.org/testlink/ |
| | 49 | * revise the basic rules of writing testcases |
| | 50 | * make sure there is only one choice for starting a book in a testcase - "Open Book" or "Create new book" |
| | 51 | * test cases cannot be limited to "up to 15 steps" if we want the steps to be simple and sigle-actioned |
| | 52 | * in the basic test plan example steps should be separated |
| | 53 | * It should be clarified that some testcases might have to have different substeps or steps inside them for the different skins |
| | 54 | |
| | 55 | Reporting Bugs: |
| | 56 | * In Analysis of Bugs: |
| | 57 | * if a bug is a TLID type it must be clarified on which step the application crashes |
| | 58 | * In Design and Implementation the attachments must be linked properly if mentioned. |
| | 59 | * The attachments' names shouldn't have spaces because you will not be able to link them properly in the ticket. |
| | 60 | * Test: Test is performed by the reporter or in some needed cases by an integrator. If the bug is not present the ticket is closed. |
| | 61 | |
| | 62 | Reviewing: |
| | 63 | |
| | 64 | |
