Edgewall Software

Changes between Version 24 and Version 25 of TracDev/UnitTests


Ignore:
Timestamp:
Jan 29, 2018, 10:53:14 PM (22 months ago)
Author:
figaro
Comment:

Added more context to unit tests

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/UnitTests

    v24 v25  
    33= Trac Unit Tests
    44
    5 Most of the Python modules in the Trac codebase are accompanied by unit tests. You should run the tests whenever making changes, to be confident you haven't broken anything. Note though that the coverage of application code by the unit tests is incomplete, so not having broken the unit tests does not mean you haven't broken the application! Unit tests do not replace manual testing.
     5Unit tests assist in developing code that meets requirements and prevents regressions when modifying code. Most of the Python modules in the Trac codebase are accompanied by unit tests. They are added as separate scripts and in their own folder `tests`.
    66
    7 Ideally, also include new unit tests for a change or enhancement, even if you are just submitting a patch. Patches that break the unit tests are a lot less likely to get integrated than patches that add unit tests for the new or changed functionality.
     7You should run the tests whenever making changes, to be confident you haven't broken anything. Note though that the coverage of application code by the unit tests is incomplete, so not having broken the unit tests does not mean you haven't broken the application! Unit tests do not replace manual testing.
     8
     9Ideally, please include new unit tests for a change or enhancement, even if you are just submitting a patch. Patches that break the unit tests are a lot less likely to get integrated than patches that add unit tests for the new or changed functionality.
    810
    911== Running the tests