Changes between Version 5 and Version 6 of DevelopmentPage/CodeTesting


Ignore:
Timestamp:
Nov 29, 2012, 5:07:15 PM (12 years ago)
Author:
Valentin Hirschi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentPage/CodeTesting

    v5 v6  
    11= IOTests =
    22
    3  The category of IOTests consists in systematically comparing a number of reference files (typically generated in previous stable versions) against the ones generated by the tested revision. These are very important as it is the only way to make absolutely sure that no border effects have been introduced. The drawback then being that they are overly sensitive and can become time consuming to update as the code evolve. Also, these tests are very inelegant if performed naively by hardcoding the reference content in the python code itself.
     3 The category of IOTests consists in systematically comparing a number of reference files (typically generated within previous stable versions) against the ones generated by the tested revision. These are very important as it is the only way to make absolutely sure that no border effects have been introduced. The drawback then being that they are overly sensitive and can become time consuming to update as the code evolve. Also, these tests are very inelegant if performed naively by hardcoding the reference content in the python code itself.
    44
    5 This is why MadGraph5 proposes an efficient way of handling these tests by proposing a managing system fully incorporated in the test_manager.py script. Also, a structure is proposed to ease new implementation of such tests by making them inherit from the generic class IOTest.
    6 
     5This is why MadGraph5 proposes an efficient way of handling these tests by proposing a managing system fully incorporated in the test_manager.py script. A structure is proposed to ease new implementation of such tests by making them inherit from the generic class IOTest.
    76== General information about the IOTests ==
    87