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
[TestNG] Make "Display disabled tests in report" configurable #369
Comments
Not relevant to me anymore. |
@MindaugasMateika I have faced the same issue as yours. Have you found another solution which does not involve code changes in allure? Thanks |
@AutomatedOwl I've started using TestNG's method selector. Either way, I was using custom annotation with parameters to tell which tests should not be run during runtime. Something like this:
Before I was using annotation transformer to add This is my method selector:
You can achieve the same thing with method interceptor but it does require TestNG 7.0-beta3 to work properly I think. Previous versions have a bug. Hope this helps. :-) |
is there a way to reopen this? i'd also like this behavior to avoid seeing skipped tests in the results without needing to add custom annotations. |
sharing some details on why this is relevant in my environment and possibly in others. we use the
or
to support a few scenarios
before upgrading allure, these tests never appeared in any report. now they do - the purple in the image reflects 11 tests with enabled=false. that throws off the pass percentage number, which was 100% passing before upgrading allure. if support is added for ignoring these tests completely in test results, we'd switch to that approach. if that support is not added, we'd likely switch all occurrences of the above patterns to
we can do that, it's just not ideal, and i suspect we aren't the only ones that liked to set enabled = false and know they'd be ignored in allure reports. |
I've reopened the issue. I hope someone will take a look at this and fix it :-) |
@MindaugasMateika thanks! |
@baev Is there any solution to the above mentioned scenario? |
any plans to fix this one? at the moment the workarounds i've seen discussed in this thread are
i'd still prefer to use |
is this issue still open? no solutions yet? |
Any chance of having this issue prioritized and implemented? I'd be happy to contribute and help implementing in case support could be provided :) |
👍 I'm ok with that. A few thoughts:
|
Cool! I will take a look at it. Thanks, mate. |
not sure. Simply add desired field to AllureTestNG, create a AllureTestNgConfig POJO with the same field, add a constructor to AllureTestNG that accepts AllureTestNgConfig, update default constructor so it load allure properties and init AllureTestNgConfig from property values and passes config to other constructor. That's should be it. And don't forget a test for that |
@baev there was this #49 issue years ago fixed to display disabled tests as skipped.
|
@baev MR is ready. Please, review whenever you have some time. |
I'm submitting a ...
What is the current behavior?
Disabled tests (
@Test(enabled = false
)) appear as unknown in the report.#275
What is the expected behavior?
Make it configurable so there would be an option to allow disabled tests to appear in report or not.
What is the motivation / use case for changing the behavior?
We have a test suite which supports the same application with different features in multiple countries. Some countries do not have features that other countries have thus we're using Annotation Transformer to disable those tests for those countries.
It would be nice to not see those disabled tests in the report as they clutter the report and create a distraction.
Please tell us about your environment:
We are not updating to the newest versions because of that behavior and we would love to avoid forking and changing this behavior in forked Allure projects.
The text was updated successfully, but these errors were encountered: