You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
When aggregate report is used, all executors are reported with the name of the parent module.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Create a project with a submodule. submodule must provide test results and activate allure reportSet report; parent module must activate reportSet aggregate.
Run
# generate child
mvn site
# generate aggregate
mvn site
Generated aggregated report show an executor named with the parent module name instead of the child module name.
What is the expected behavior?
Executor should be named with the child module name
Where is the bug
aggregate report (AllureAggregateMojo) triggers AllureGenerateMojo#copyExecutorInfo for each inputDirectories, so for each child module allure-results folder. It overwrites the correctly generated file (generated by report on child module) with a new one with buildName =
I think that copyExecutorInfo should be called only for inputDirectories related to the current module, even when aggregate report is done.
What is the motivation / use case for changing the behavior?
Report consistency
Please tell us about your environment:
Allure version: 2.5.0
Test framework: junit4 (not test framework related I think)
Hi any update in this issue, i am not getting Maven and Igloo-Parent, i am creating the executor.json file from the code and I have only 1 attribute in it that is the tester name {"Tester":"ABCD"}, not sure what I am doing wrong but I am getting a hate symbol and name is displayed as "Unknown
"
I'm submitting a ...
What is the current behavior?
When aggregate report is used, all executors are reported with the name of the parent module.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Create a project with a submodule. submodule must provide test results and activate allure reportSet report; parent module must activate reportSet aggregate.
Run
Generated aggregated report show an executor named with the parent module name instead of the child module name.
What is the expected behavior?
Executor should be named with the child module name
Where is the bug
aggregate report (AllureAggregateMojo) triggers
AllureGenerateMojo#copyExecutorInfo
for each inputDirectories, so for each child module allure-results folder. It overwrites the correctly generated file (generated by report on child module) with a new one withbuildName
=I think that copyExecutorInfo should be called only for inputDirectories related to the current module, even when aggregate report is done.
What is the motivation / use case for changing the behavior?
Report consistency
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: