Iramis Valentin

@youtux @olegpidsadnyi Any insights on this? I am also having this issue.

So I have a few questions. 1. If all the scenarios are collected, do they automatically map to the `test_*.py` files? a. If they are automatically mapped, how do they...

OK I think I understand. Another question I have is: Are feature file names such as `1_SOME_FEATURE-22.feature` allowed?

So in my particular folder structure I have the following: ``` Tests features mobile login 1_login-2.feature web login 1_login-2.feature step_defs mobile login login_step_fixtures.py conftest.py web login login_step_fixtures.py conftest.py conftest.py (root...

Hmmm interesting. Would that require decorating each `def test_X():` with `@scenario()`? It seems like the small amount of documentation on the `scenarios` shortcut implies that using it removes the need...

AH, interesting! So I assume you have multiple `test_*()` function definitions inside of your `test_my_project.py`? I've been finding difficulties with manually mapping each individual test function with the correct feature...

Ok, thank you for the documentation! It's leading me down a trail of more documentation but I think I have a better picture of how things are currently being collected...

Has there been any movement on implementation on this? @bubenkoff You mentioned this could be implemented as a hook, how would someone go about doing that?

@BeyondEvil I recently researched into adapting pytest-selenium to function in multiple fixture scopes (session, module, class, etc) due to a parallel use-case to @larsrinn. I came to the same conclusion...

Is there any update on this? Is this already supported? Does pytest-bdd or allure even need to explicitly "support" each other or do they both adhere to the same reporting...