Changes between Version 1 and Version 2 of TestingGuidelines


Ignore:
Timestamp:
Dec 10, 2010, 1:16:08 PM (14 years ago)
Author:
FrederikHeber
Comment:

typo fix

Legend:

Unmodified
Added
Removed
Modified

  • TestingGuidelines

    v1 v2  
    103103==== Unit test ====
    104104
    105 Calling single unit tests is even easier. Assumptions from above, we want to call '''FormulaUnittest''' and reside in '''./build''', enter
     105Calling single unit tests is even easier. Assumptions from above, we want to call '''!FormulaUnittest''' and reside in '''./build''', enter
    106106{{{
    107107src/unittests/FormulaUnittest
    … …  
    113113At the very last, we have to talk about what to do with the test if something is broken. If a unit test is broken, you might only modify the code directly.
    114114When it is a regression test, you can modify the return value to state that something will not work.
     115However ...
    115116
    116  '''However beware when changing tests! '''
     117 '''Beware when changing tests! '''
    117118
    118119These should never be done lightly and changes to tests HAVE to be given in full in the description of the commit to the repository, also state why the change was necessary. Maybe the test was not complete or faulty itself.