Changes between Version 120 and Version 121 of DeveloperGuidelinesTesting


Ignore:
Timestamp:
08/15/11 18:41:26 (14 years ago)
Author:
Mike A
Comment:

note about commenting out tests and encouraging writing tests without fixes.

Legend:

Unmodified
Added
Removed
Modified

  • DeveloperGuidelinesTesting

    v120 v121  
    163163  * If they don't pass, fix or leave out the code that is causing failure.
    164164  * If the tests themselves are broken due to e.g. and API change, update them. Never paste actual output as expected output.
    165 
     165  * Don't comment out or remove a test just because it fails. For that matter, if you come across a bug, but don't have time to fix it, it is a good practice to write a test that shows it failing. It's much better than a TODO comment, because it can't be forgotten about, and it will probably be a lot more useful than a bug report for whoever will eventually fix it.
    166166=== Javascript unit tests ===
    167167Selenium enables functional testing but not really unit testing other than reporting the results of javascript test runs.