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

Merged report with multiple suites #69

Open
ccsuperstar opened this issue Jul 26, 2021 · 7 comments · May be fixed by #105
Open

Merged report with multiple suites #69

ccsuperstar opened this issue Jul 26, 2021 · 7 comments · May be fixed by #105
Assignees

Comments

@ccsuperstar
Copy link
Contributor

ccsuperstar commented Jul 26, 2021

When I run my test runs in parallel, the merged html report does not contain all the suite titles. I think this is because the distribution of tests is done in such a way that each /_data/parallel_* file does not always contain tests from each suite.

Also, the execution time in the final report is not the maximum execution time.

Before v1, I had made a modification, with a report template file which match with our need, but I'm looking forward to your ideas!

@vansari
Copy link
Collaborator

vansari commented Jul 26, 2021

Hi @ccsuperstar

This is the class where I did not have enough time for a UnitTest. But as you can see it is very useful to have a test which tests the expected result.

If you can provide some html test results it would be very helpful.

If not it's also okay 😉

@ccsuperstar
Copy link
Contributor Author

If you use for example these 3 html reports (report_1.html, report_2.html, report_3.html), and you run the merge report command, as it is the first html report that is used to define the suite titles, you will have only the title Acceptance in report.html file
reports.zip

While in the other reports, you have Api, Bdd, etc

So, either you have to use a template, or you have to parse all the reports to have all the suites

@vansari
Copy link
Collaborator

vansari commented Jul 31, 2021

hi @ccsuperstar

is this the expected report what you want?
(Its manually changed for a preview)
expected_report

@ccsuperstar
Copy link
Contributor Author

Yes it's the expected report!

@reinholdfuereder
Copy link
Contributor

reinholdfuereder commented Apr 21, 2022

I think I might suffer under the same (or very similar) problem:

  • Background:
    • First there is a "serial" Codeception test execution with (a) all (fast) PhpBrowser tests and (b) some (non-parallel-working) WebDriver tests (because they temporarily manipulate something in the DB -- yes, very ugly, but it is as it is; pragmatic colleagues...)
    • Then there are a few "parallel" sets with parallel exeuction of slow WebDriver tests
  • Result:
    • Due to starting with the "serial" HTML report all the "parallel" HTML report results are merged to the first and thus wrong section/suite (but the second suite is there too, because it is part of the first "serial" HTML report too)
    • Screenshot: image
    • Files: merged-html-original-with-bug.zip
  • Expected result:
    • Screenshot (sorry for unfortunately having used a slightly different test set with 2 skipped tests and obviously a new run with different timings):
      image

@reinholdfuereder reinholdfuereder linked a pull request Apr 21, 2022 that will close this issue
@reinholdfuereder
Copy link
Contributor

@vansari My PR #105 fixes my problem and I think this issue here => thanks in advance for reviewing and merging

@vansari
Copy link
Collaborator

vansari commented Nov 20, 2022

@reinholdfuereder Is it possible that you add a test for your changes?

@vansari vansari self-assigned this Nov 20, 2022
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.

3 participants