Edgewall Software

Changes between Version 25 and Version 26 of TracDev/UnitTests


Ignore:
Timestamp:
Feb 2, 2018, 11:43:47 PM (7 months ago)
Author:
Ryan J Ollos
Comment:

Reword.

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/UnitTests

    v25 v26  
    33= Trac Unit Tests
    44
    5 Unit 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`.
     5Unit tests assist in developing code that meets requirements and prevent regressions when modifying code. Most of the Python modules in the Trac codebase are accompanied by unit tests. The test modules are found in the `tests` directory of each package directory.
    66
    7 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.
     7You should run the tests whenever making changes, to be confident you haven't broken anything. Note however 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.
    88
    9 Ideally, 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.
     9Please include unit tests that provide coverage 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.
    1010
    1111== Running the tests