4ed7701b47
Split header tests accordingly i.e. test core headers as part of core tests, numeric extension headers as part of numeric tests, etc. It extends the convention of sub-directories already established in `include/boost/gil` directory. It is sensible to follow it in other areas of the source tree (i.e. `test/`, `doc/` and `benchmark/`). Another important reason to move the tests is to enable removal of the top-level `Jamfile` with all its definitions of test-specific requirements. The top-level `Jamfile` is not advised, especially if it specifies build requirements like C++ language version. Those affect non-tests builds e.g. documentation, causing failures during generation of HTML documentation (leads to missing docs). |
||
|---|---|---|
| .. | ||
| channel.cpp | ||
| CMakeLists.txt | ||
| error_if.cpp | ||
| gil_reference_checksums.txt | ||
| image.cpp | ||
| Jamfile | ||
| performance.cpp | ||
| pixel_iterator.cpp | ||
| pixel.cpp | ||
| README.md | ||
| recreate_image.cpp | ||
| sample_image.cpp | ||
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.