Rolf Krahl

Many thanks for your contribution and please apologize for the very late reply! I needed some time to really look into this and didn't got around to do that earlier....

I'm not sure if I like the idea. I see at least two issues: 1. The use of magic names. Note that "all" is a perfectly valid name for a...

There is no direct way to depend on all parameterized test instances of one test for the moment. What you can do is to collect all parameter values in a...

@somnambWl, I need to add another remark on your example: you pass the same parameter value `True` twice to your `test_a`. Was this intended? This makes things a little bit...

As a conclusion, I'm considering to add a helper function `get_param_instances(test_name)` that takes the name of a test as argument and returns a list of strings with the names of...

It suffers from the same consistency issue as the proposal in #19. Consider: ```python import pytest def instances(name, params): def vstr(val): if isinstance(val, (list, tuple)): return "-".join([str(v) for v in...

> Pytest-dependecy is grossly incomplete without test ordering. It actually introduces to pytest a new logical execution order, but without any engine to enforce it. "Just" skipping is implemented. Adding...

Actually, that would be my question: if `pytest-order` already does the job and even explicitly supports `pytest-dependency`, why should we duplicate that effort here? I rather tend to solve this...

I still prefer to keep the scope of the plugin focused. `pytest-dependency` is about skipping tests when running them makes no sense because the prerequisites are not in place. Reordering...

> I'm sure there are some cases that are not covered in `pytest-order`, but if such a case will be found, it shall be filed as a bug in `pytest-order`...