Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Codeception Tests that contain @env do not execute due to an Allure import error message #32
Comments
|
If we add this line
|
does not work in my case |
|
and dont see how it's going to work
config structure should be something like :
|
|
Summon @kouratoras |
|
@Stybbe123 just tested and works fine. Did you get the latest |
|
"allure-framework/allure-codeception": "~1.2.4" latest available release, plus your changes. |
|
There is no release with that fix yet, only available to
|
|
tested again, works fine @ dev-master |
I'm submitting a ...
What is the current behavior?
When you have a Codeception test that includes a @env Test Annotation, like the following, and you run it you receive an Allure related error message:
Example Test
Stacktrace
What is the expected behavior?
I should be able to list a non-allure tag in the
codeception.ymlfile and have Allure ignore those tags.Other Information
After the following commit, 5088ee4f7a6f76dfc4d664d4d2ac8ebd2697de01, was made our Codeception project no longer runs when the @env annotation is included in a Test.
After reverting some of the changes that were made to the _initialize function our Tests began running without the above error.