8e7bda62f5
Document maintenance rules of `test/legacy/` content. Motivation to move the `test/legacy/` is to: * clarify status of those tests * make it easier to run tests selectively * separate new/upcoming feature-specific tests from those all-in-one tests. Other changes: Rename `gil_test_common.hpp` to `unit_test.hpp` to make it clearer it acts as `boost/test/unit_test.hpp proxy`. Remove `<include>$(BOOST_ROOT)` from `Jamfile`-s as unnecessary.
463 B
463 B
Boost.GIL Legacy Tests
These are GIL's original, comprehensive, all-in-one test suits.
Rules of maintenance:
- Run the legacy tests as part of CI builds and regression tests.
- Keep as reference.
- Do NOT extend.
- Do NOT refactor.
- Modify ONLY if absolutely necessary (a bug found in the tests).
Add new test suites, with new test cases, even if their functional coverage is the same as of the legacy tests.
See CONTRIBUTING.md.