Sylvain Marié

Any progress on this issue ? I have the same problem: both `.coveragerc` `[report]` section and `setup.cfg` `[coverage:report]` configurations are ignored by `codecov`. @interDist : > everybody who complained about...

My bad: it seems to work now. The secret seems to PUSH the .coveragerc file as it is not taken into account locally (the .coverage file and generated coverage.xml report...

Afterthough: these seem to be usefool pytest goodies, but are not documented. They should be

Hi @marshall7m, thanks for the feedback ! I am deeply sorry, but I have trouble getting your example. Would you be kind enough to try rewriting it in the following...

Any progress on this @marshall7m ? Just to be sure you found a way out

This pytest example ```python @pytest.mark.parametrize( "a,b,expected", [ pytest.param( datetime(2001, 12, 12), datetime(2001, 12, 11), timedelta(1), id="forward" ), pytest.param( datetime(2001, 12, 11), datetime(2001, 12, 12), timedelta(-1), id="backward" ), ], ) def...

After sleeping on this I think the right order would better be: - 1. `@parametrize` does not need to create a test wrapper anymore. It needs to stop creating `ParamAlternative`s...

Another way to say the above is "before I thought that fixture unions were the core and parametrize would reuse this, but we have to revert this pattern: a fixture...

@phistep do you remember what was your need about this ? (from #147) . Do you still think that the 4 filters mechanisms ([described here](https://smarie.github.io/python-pytest-cases/#filters-and-tags)) are not satisfying for daily...

Thanks for the feedback @Jasha10 ! I *think* that the workaround for issue #174 should solve your issue as well, did you try ? ```python # test_foo.py from pytest_cases import...