Changes between Version 8 and Version 9 of SCS_TEST_TRACKING_MAINTENANCE_R4


Ignore:
Timestamp:
07/04/09 13:44:37 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SCS_TEST_TRACKING_MAINTENANCE_R4

    v8 v9  
    1212 * Add the newly created test cases to a test plan. Use the current revision of the trunk for the test case 
    1313 * Schedule executing of the test plan. 
     14 * Optional - create test cases for non-fixed bugs 
    1415 * Optional - execute the test plan and link the result here 
    1516== Task result == 
    … …  
    3031 * A test case for default sizes of video, image, pdf and books is needed. This will be fixed later. This should not be a regular test. 
    3132 * A keyboard test is needed for test frames. This should be discussed with the developers. This is related to the "Shift" bug. 
    32  * App file dialogs test case should be split for the various file dialogs. All of them should be covered. Consisitency should be ensured. #1714 #1738 
     33 * App file dialogs test case should be split for the various file dialogs. All of them should be covered. Consisitency should be ensured. #1714 #1738 #1755 #1756 
    3334 * Embedding book test case should include embedding the book twice. Probably a new test case ensuring the resources can be duplicated will be OK. #1722 
    3435 * A persistence test case is needed. This can be done by a general test case covering most of the functionality or split into pieces (Each functionality test case to include save and reload. If one test case is created, it should be regular. #1725, #1726, #1727, #1728, #1729 ... 
    35   * A good idea is to create one fast test - that tests persistence of all elements, and then tests for specific things, that should be tested if the master test fails. 
    36  * To link testcase frame name #1731 human readability should be ensured. 
     36  * A good idea is to create one fast test - that tests persistence of all elements, and then tests for specific things, that should be tested if the master test fails. This can be an auto test. 
     37 * To link testcase frame name #1731 human readability should be ensured. #1750 
    3738 * Browser frame test cases should be created 
    3839 * Book desktop test case should be created #1742, #1743 
     40 * Zoom TLID:799 should be expanded with #1745 
     41 * Sticky test case is needed #1752 
     42 
     43 * These were all fixed bugs. Non-fixed bugs design will be postponed for now. 
     44 
    3945= Implementation = 
    4046^(Describe and link the implementation results here (from the wiki or the repository).)^