-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2] Use external config instead of arguments in phpunit.xml #66
Comments
@remorhaz Thanks for your great work on this! It looks cool! I have an issue with it outputting the reports to paths relative to the test rather than relative to the project path. Do you think this will fix that? |
Well, @mikepsinn, could you please provide more information about your configuration and library versions? |
@remorhaz Thanks for the reply! :D I'm still using PHPUnit 7.5.20, so maybe that's the issue. I'm using allure-phpunit 1.2.4. I've tried using both of the configs below. It's not a super-big deal, so I hate to take up your time with it. I was just curious if your new implementation might fix it. Thanks!
|
That's quite old version. Our v2 prototype supports only PHPUnit 9/PHP 8. Allure extension just uses directory that is set by PHPUnit, maybe old versions of the tool had some bug, but I think that as a first step to solution you should update your environment. |
External config will be much more extendable and will virtually never break BC. The only optional argument will be the path to config (which will set by default to
config/allure.phpunit.config.php
).The text was updated successfully, but these errors were encountered: