Open michaelmckinsey1 opened 3 months ago
Depends on ~#193~
depends on ~#181~
@ilumsden Tests that use the thicket_axis_columns
fixture are already parametrized, since thicket_axis_columns
is parametrized itself. Unlike the other fixtures, which are lists of files, thicket_axis_columns
and stats_thicket_axis_columns
create the Thickets in the fixtures.
So running python -m pytest thicket/tests/test_concat_thickets.py::test_filter_stats_concat_thickets_columns
results in:
0.44s call thicket/tests/test_concat_thickets.py::test_filter_stats_concat_thickets_columns[Intersection-FillPerfdata]
0.41s call thicket/tests/test_concat_thickets.py::test_filter_stats_concat_thickets_columns[Intersection-NoFillPerfdata]
0.33s call thicket/tests/test_concat_thickets.py::test_filter_stats_concat_thickets_columns[Union-FillPerfdata]
0.33s call thicket/tests/test_concat_thickets.py::test_filter_stats_concat_thickets_columns[Union-NoFillPerfdata]
This PR proposes to expand running the unit tests for (1) Thickets with intersection trees (default is union) and (2) Thickets without filling the performance data (default is filling the performance data). Therefore, testing for each combination would run all the unit tests for 4 types of Thickets:
Example of using parametrized fixtures from pytest docs
When tests fail, we can see which configuration of parameters failed:
We can run single tests for a single set of parameters by specifying them to pytest