Changes between Version 25 and Version 26 of TracDev/UnitTests
- Timestamp:
- Feb 2, 2018, 11:43:47 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/UnitTests
v25 v26 3 3 = Trac Unit Tests 4 4 5 Unit tests assist in developing code that meets requirements and prevent s 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`.5 Unit 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. 6 6 7 You should run the tests whenever making changes, to be confident you haven't broken anything. Note thoughthat 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.7 You 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. 8 8 9 Ideally, please include new unit testsfor 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.9 Please 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. 10 10 11 11 == Running the tests