Changes between Version 5 and Version 6 of PLATFORM_STANDARDS_MANUAL_TESTS


Ignore:
Timestamp:
09/18/09 12:46:50 (12 years ago)
Author:
vanya
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PLATFORM_STANDARDS_MANUAL_TESTS

    v5 v6  
    44'''Important note:''' This page is being worked on. You should regularily check for updates. 
    55 
     6 
    67= How to write manual tests = 
    7 This document contains requirements and guidelines for writing good manual test cases. Here you will find information about what should be tested and how to use our [http://sophie2.org/testlink Testlink] server. Rules for reviewing will be provided as well. When writing manual tests, do not forget the general guideline of the project: '''Work towards the goal! ''' 
     8This document contains requirements and guidelines for writing good manual test cases. Here you will find information about what should be tested and how to use our [http://sophie2.org/testlink TestLink] server. Rules for reviewing will be provided as well. When writing manual tests, do not forget the general guideline of the project: '''Work towards the goal! ''' 
    89 
    910== Test cases == 
    10 We use a [http://sophie2.org/testlink Testlink] server for writing, executing and tracking manual test cases. The homepage of the Testlink project is http://testlink.sourceforge.net/docs/testLink.php. 
     11We use a [http://sophie2.org/testlink TestLink] server for writing, executing and tracking manual test cases. The homepage of the Testlink project is http://testlink.sourceforge.net/docs/testLink.php. 
    1112 
    1213Here follow some basic rules about how to write test cases: 
     
    1718 * Use cases must be organized by categories. 
    1819 
    19 The following basic test plan should be executed on every iteration. It consists of basic functionality that should always work: 
    20  * Open Sophie2 
    21  * Create/open a new book 
    22  * Add/delete pages 
    23  * Add/delete frames 
    24  * Save/close the book 
    25  * Exit Sophie2 
     20On every iteration these are the testplan cases on some basic functionalities that should be executed and that should always work: 
     21||'''Testcase:'''||'''Expected Results:'''|| 
     22|| Start Sophie2.|| Sophie2 should start in default skin with open left, bottom and right flap.|| 
     23|| Create a new book.|| A new book should be created.|| 
     24|| Add a page to the book.||A new page should be added to the book.|| 
     25|| Add a resource frame to a page of the book.|| A resource frame is added to the page.|| 
     26|| Delete a frame from a page in the book.|| The wanted frame is deleted from the page.|| 
     27|| Delete a page from the book.|| The wanted page is deleted from the book.|| 
     28|| Save the book.|| The book is saved.|| 
     29|| Close the book.|| The book is closed.|| 
     30|| Open an existing book.|| The book is loaded.|| 
     31|| Exit Sophie2 .|| Sophie2 is closed.|| 
    2632 
    27 In the progress of testing, this plan will be expanded and more test plans will be added. 
     33All testcases must  
     34 * begin with either one of these choices: 
     35||'''Steps:'''||'''Expected Results:'''|| 
     36||1. Start Sophie2.||1. Sophie2 should start in default skin with open left, bottom and right flap.|| 
     37||2. Create a new book.||2. A new book should be created.|| 
     38or 
     39||'''Steps:'''||'''Expected Results:'''|| 
     40||1. Start Sophie2.||1. Sophie2 should start in default skin with open left, bottom and right flap.|| 
     41||2. Open an existing book.||2. The book is loaded.|| 
     42 
     43and end with these steps: 
     44||'''Steps:'''||'''Expected Results:'''|| 
     45||...||...|| 
     46||8. Save the book.||8. The book is saved with all the made changes.|| 
     47||9. Close the book.||9. The book is closed.|| 
     48||10. Open the saved book.||10. The book should load with all the made changes before saving.|| 
     49 
     50There is no limit to the number of steps in a testcase. A testplan consists of number of existing testcases. The testcases in a testplan should be picked in a way that would lead to the expected result after executing them. In the progress of developing the project different testplans will be added depending on the various expectations towards the testplan results. 
    2851 
    2952== Reporting bugs == 
     
    3760 * A link to the user documentation describing this task. 
    3861 * A link to the release documentation if the result of this task will be part of the next release. 
    39  * Links to use cases in [http://sophie2.org/testlink Testlink] where applicable. 
     62 * Links to use cases in [http://sophie2.org/testlink TestLink] where applicable. 
    4063  * related test cases should be considered and listed as well. 
    4164 * Links to all auto tests related to this tasks. 
     
    4568 * A brief explanation of the bugs reported with links to their trac tickets. 
    4669  * links to related bugs should be provided as well. 
     70 * Links to the related attachments for testing should be provided if needed. 
    4771 
    4872=== Scoring === 
     
    5478 * Score 5 (pass): The testing phase is structured according to the standards and there's nothing more to be added - it's perfect in such a way that a person who is not quite familiar with the project can clearly see that the feature(s) is/are implemented really well. 
    5579 
    56 All reviews should be motivated. A detailed comment about why the testing phase fails is required. For a score of 3 a list of things that could be better should be provided. Comments are encouraged for higher scores as well. Non-integer scores are STRONGLY disencouraged. If you give the testing a score of 3.5, then you probably have not reviewed it thoroughly enough and cannot clearly state whether it is good or not. Once the testing phase has been reviewed, it cannot be altered. If you think it is wrong, you should request a super review. Currently all super reviews should be discussed with Milo. Make sure you are able to provide clear arguments of what the testing lacks before you request a super review. 
     80All reviews should be motivated. A detailed comment about why the testing phase fails is required. For a score of 3 a list of things that could be better should be provided. Comments are encouraged for higher scores as well. Scores should be in the range from 1 to 5 with a recommended step 1. A 0.5 step is also possible but if you give the testing a score of 3.5 then you probably have not reviewed it thoroughly enough and cannot clearly state whether it is good or not. Integer numbers are recommended. Once the testing phase has been reviewed, it cannot be altered. If you think it is wrong, you should request a super review. Currently all super reviews should be discussed with Milo. Make sure you are able to provide clear arguments of what the testing lacks before you request a super review. 
    5781 
    5882= Comments =