I got your point, Reece, but maybe it would be better to extend the pytest
default config instead of making the plugin.
Anyway, it's a good feature. 👍
чт, 11 июл. 2019 г. в 01:14, Reece Hart :
> Jim- Interesting. Definitely related. Thanks for sharing that.
>
> Arseniy- The major motivation is to
Jim- Interesting. Definitely related. Thanks for sharing that.
Arseniy- The major motivation is to disable certain tests by default. I
tried to outline the shortcomings of current mechanisms in the README, but
probably need a bit more. In any case, using -m expressions in the cfg file
conflicts wi
Hello,
Why don't you want to add markers to pytest.ini config?
For now, you can add custom run options to the pytest.ini file.
[pytest]addopts = -m my_marker
But I agree that separate option for run marked tests would be better.
[pytest]addopts = -s -v
markers_to_run = my_marker1, my_marker2
Nice!
It looks similar to something that I did a while back:
https://github.com/Projectplace/pytest-tags
--
Jim Brännlund
jimbrannl...@fastmail.com
On Tue, Jul 9, 2019, at 3:35 AM, Reece Hart wrote:
> I would appreciate feedback/code review on a pytest plugin (my first!) that I
> wrote to
I would appreciate feedback/code review on a pytest plugin (my first!) that
I wrote today to simplify the use of pytest markers for optional tests.
Code is at https://github.com/reece/pytest-optional-tests. tests and pypi
deployments (via travis) are already available.
I'm open to all comments: ut
