Skip to content
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

Incorrect display of tests structure when use common test project in multiple solutions #394

Open
vzhik54 opened this issue Oct 12, 2023 · 0 comments

Comments

@vzhik54
Copy link

vzhik54 commented Oct 12, 2023

Hi team!

I have several solution like:
Solution.One
*****Project.One
*****TestProject.One

Solution.Two
*****Project.Two
*****TestProject.Two

Also I have common solution like
Solution.Common
*****CommonProject
*****CommonProject.Tests

CommonProject.Tests added to TestProject.One and TestProject.Two via project reference

TestProject.One project has 1 test
TestProject.Two project has 1 test
CommonProject.Tests project has 1 test

Once the tests are done I collect all allure files from allure-results directories of test projects into one common allure-results directory. And I generate and open report then.

I noticed that the actual number of tests is not equal to what is expected in allure report.
I expect to see the number of tests equal to 4.
But number of tests equal to 3.

I found out that tests structure is incorrect on package tab of report:
Expected like this:
TestProject
*****One
**********Tests 1
**********CommonProject.Tests 1
*****Two
**********Tests 1
**********CommonProject.Tests 1
image

Actual:
CommonProjects.Tests 1
TestProject
*****One.Tests 1
*****Two.Tests 1
image

Workaround:
In order to fix this issue I parse "*-result.json" files and add solution name to start of value of following properties:
historyId
fullName
labels["name": "package"] value

And then I collect files to generate report.

I have prepared a sample in archive to demonstrate this troble. Also i added json files of allure report there
sample.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant