We migrated our test framework from jUnit4 to jUnit 5 to make use of dynamically generated tests.
After doing so and creating the first bunch of test-tests to test the framework, we had to find out that Allure can't properly display the resulting tree structure. Problem occurs locally via allure-cli and via allure-jekins-plugin.
Our test structure:
Collections of tests is run by methods annotated with @TestFactory
This collection of tests are basically DynamicContainers consisting of DynamicNodes that make the single sub-tests or test steps.
instead of DynamicTests one may also add another DynamicContainer, that grows the tree even more
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
I will add an exaple when I have some more time (sorry for that), but it is sufficent to create jUnit5-Tests from @TestFactories that run one or more DynamicTestss contained in a DynamicContainer.
What is the expected behavior?
Allure should be capable of visualizing the tree structure / test hierarchy correctly.
What is the motivation / use case for changing the behavior?
I think jUnit5-support is not complete without properly supporting DynamicContainers containing DynamicTests or further DynamicContainers containing DynamicTests or further DynamicContainers...
Please tell us about your environment:
Allure version
2.13.1
Test framework
jUnit@5.4.0
Allure integration
allure-junit5@2.13.1
Generate report using
allure-maven@2.10
Other information
Log-Output of Mvn-Plugin
[INFO] Allure installation directory *****/.allure
[INFO] Try to finding out allure 2.13.1
[INFO] Generate Allure report (report) with version 2.13.1
[INFO] Generate Allure report to ****/allure-maven-plugin
[INFO] Found results directory ****/allure-results
[INFO] Can't find information about categories.
[INFO] Generate report to *****/allure-maven-plugin
Report successfully generated to *****/site/allure-maven-plugin
[INFO] Report generated successfully.
I'm submitting a ...
What is the current behavior?
We migrated our test framework from jUnit4 to jUnit 5 to make use of dynamically generated tests. After doing so and creating the first bunch of test-tests to test the framework, we had to find out that Allure can't properly display the resulting tree structure. Problem occurs locally via allure-cli and via allure-jekins-plugin.
Our test structure:
@TestFactory
DynamicContainer
s consisting ofDynamicNodes
that make the single sub-tests or test steps.DynamicTest
s one may also add anotherDynamicContainer
, that grows the tree even moreIf the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
I will add an exaple when I have some more time (sorry for that), but it is sufficent to create jUnit5-Tests from
@TestFactories
that run one or moreDynamicTests
s contained in aDynamicContainer
.What is the expected behavior?
Allure should be capable of visualizing the tree structure / test hierarchy correctly.
What is the motivation / use case for changing the behavior?
I think jUnit5-support is not complete without properly supporting DynamicContainers containing DynamicTests or further DynamicContainers containing DynamicTests or further DynamicContainers...
Please tell us about your environment:
Other information
Log-Output of Mvn-Plugin