Changes between Version 5 and Version 6 of PLATFORM_STANDARDS_AUTO_TESTS_R1


Ignore:
Timestamp:
01/16/09 14:12:37 (16 years ago)
Author:
boyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PLATFORM_STANDARDS_AUTO_TESTS_R1

    v5 v6  
    44[[TicketQuery(summary=PLATFORM_STANDARDS_AUTO_TESTS_R1, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] 
    55 
    6  
    76= Analysis = 
    87 
    98== Overview == 
    109 
    11   The aim of this revision of the task is to improve the auto testing infrastructure, conventions etc. 
     10The aim of this revision of the task is to improve the auto testing infrastructure, conventions etc. 
    1211 
    1312== Task requirements == 
     
    5251= Design = 
    5352 
     53The [wiki:PLATFORM_STANDARDS_AUTO_TESTS] page is out of date because it reflects the old testing structure of Veda. It will be recreated using the following structure: 
     54{{{ 
     55|_Platform Standards Auto Tests 
     56|__General conventions 
     57|__Unit testing 
     58|___Writing 
     59|___Reviewing 
     60|__Integration testing 
     61|___Writing 
     62|___Reviewing 
     63|__System testing 
     64|___Writing 
     65|___Reviewing 
     66|__Running tests 
     67|__Useful links 
     68|_Comments 
     69}}} 
     70Here follow the contents of each section: 
     71 * Platform Standards Auto Tests - an overview of what the page is about. 
     72 * General conventions - rules for writing all kind of tests and javadoc. 
     73 * Base classes - explanation of the usage of the base testing classes. 
     74 * Unit/Integration/System testing - a description of the different scopes of testing - info from the currently linked wiki pages should be extracted here. 
     75  * Writing - what classes should be tested and how. 
     76  * Reviewing - how to judge if a given test is good enough; how to review the testing phase of tasks. 
     77 * Running tests - a description of how to run a given test or all tests (via Maven or Hudson). 
     78 * Useful links - Links for further reading on the topic. 
     79 * Comments - Comments for improving the standards that will be incorporated into the page in the next revision. 
     80 
     81Everyone has been asked to give suggestions for improving the standards in the Comments section. These will be considered in the implementation phase. 
     82 
    5483= Implementation = 
    5584