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

jUnitReport.xml contains wrong data with smart sharding #618

Closed
andreschab90 opened this issue Nov 13, 2019 · 4 comments · Fixed by #666
Closed

jUnitReport.xml contains wrong data with smart sharding #618

andreschab90 opened this issue Nov 13, 2019 · 4 comments · Fixed by #666
Milestone

Comments

@andreschab90
Copy link

I am using smart sharding and i recognized the the jUnitReport-xml file contains wrong data compared to real results of the matrixes. I can provide you some xml files for debugging if needed

@bootstraponline
Copy link
Contributor

I'll need more info to identity, reproduce, and resolve the issue.

@andreschab90
Copy link
Author

andreschab90 commented Nov 13, 2019

i had a look in the links to inside the junit file.
I have a test A which fails, but the junit reports successful, because the link for this test-case points to the wrong matrix, to a successful one.

I have a matrix with 6 testcases, so the url should be present 6 times in the file, but it's only 2 times.

i guess some testcases gets the wrong matrix assigned

If you need the files then i can send them over to you via slack for example

@bootstraponline
Copy link
Contributor

Thanks! I'll take a look soon.

@bootstraponline
Copy link
Contributor

bootstraponline commented Nov 17, 2019

Debugged. Root cause is FTL does not produce XML files for all failed matrices. Flank currently detects failures by parsing the XML. If a failed matrix doesn't produce an XML then they'll be missing from the Flank XML report.

Moving to API based results fetching may solve the issue. However the FTL API is currently incomplete which blocks this work.
#545

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

Successfully merging a pull request may close this issue.

2 participants