-
Notifications
You must be signed in to change notification settings - Fork 117
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
parallel reporting #30
parallel reporting #30
Comments
This plugin uses custom reporter which prints the results in console and doesn't create any html reports. You need to create your own reports using various reporting plugins in the market. @tnicola mentioned that he will be working on html report in near future. so you can create using this plugin. |
The HTML report generated using mochawesome reporter seems to be listing only the details of the last executed spec file. Is there any specific configuration that I am missing while using this plugin for parallel testing ? |
You can use this: |
How can I keep using mochawesome as I used to do? I noticed that when I run the script for parallel execution, this is hardcoded: If I try to set the configFile parameter, the execution fails in the end because can't find the runner-results folder. |
I have been struggling with the same.
…On Wed, Nov 17, 2021 at 9:16 AM vicente.ruiz ***@***.***> wrote:
How can I keep using mochawesome as I used to do? I noticed that when I
run the script for parallel execution, this is hardcoded:
"--reporter" "cypress-multi-reporters" "--reporter-options"
"configFile=/Users/user/workspace/myProject/test-folder/multi-reporter-config.json"
and the multi-reporter-config.json file is overwritten every time I launch
the tests.
If I try to set the configFile parameter, the execution fails in the end
because can't find the runner-results folder.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#30 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMR4WMK4IGJKYGAW4S22HH3UMO2K5ANCNFSM4ZNCS2QA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I was confused by this too. It seems you cannot specify configFile, but you can pass in everything that was in your config file as args. |
|
I'm struggling with utilizing the reporter.config.json file. For my command, I'm running
and the generated file reflects the reporter option:
but none of the options set within the reporter.config.json file are being respected. Any ideas? |
too less data to understand the problem, At first tell me if the options are respected when you try run command by I will show you my full command
and and then in my reporter config file I'm using more that one reporter
maybe try use |
any luck with this, any one? Thanks |
any update on this issue? mochawesome is only reporting the last run tests. |
I have set it up as below and it's working for me... On my
And I can execute the test using a
|
I had a different approach for mochawesome in my project. There's some elements in common with previous solutions : In
So my The workflow in all solutions is the same :
I have 0 mochawesome configuration in my Sources for this solutions comes from this thread, and Cypress doc : https://github.com/cypress-io/testing-workshop-cypress/blob/master/slides/09-reporters/PITCHME.md#mochawesome |
This seems to work perfectly, the only issue I have is that the Screenshots are not appearing in the report. Is there some other config I'm missing? |
solved this issue as following: my configuration File: const { defineConfig } = require("cypress"); e2e: {
} in package.json i have the following script: where: |
The solution above is working fine. The only issue I am facing is that since I am running with 4 threads, 4 html files generated at the end of the run. Any idea how to to get 1 html instead of 4? |
https://github.com/PremierTechDigital/cypress-parallel-report For those interested, I built a repository to demonstrate our final solution to run Cypress parallel and get a report. At the end, we have one report, with some tweaks so the number of success and failures can bubble up properly if you have nested describes. This repo helped in this issue : LironEr/cypress-mochawesome-reporter#44 (comment) and there's a new version of cypress mochawesome reporter that should handle this properly. I didn't had time to test it though. |
|
Check out the setup guide |
The new released version of cypress-mochawesome-reporter is working perfectly with cypress-parallel. There is just one issue when ruuning the tests in the build pipeline: Previously when the tests failed in the build pipeline, build failed with exit code based on the number of tests failed. But not the case anyomore after using the parallel execution. Any idea how to get the build failed with exit code in cypress-parallel incase some tests failed? Thanks |
I'm just having the same issue. Looks like no matter how many tests fail now on CI (using github actions) - the job always ends up as 'passed' |
@LironEr @lems3 @scoca91 @barnie-karbonhq |
Just released a new version of
Will set the exit code to the number of failed tests. |
how to use cypress-parallel with https://www.npmjs.com/package/multiple-cucumber-html-reporter?. |
Hello,
For some reason the parallel run doest work with reporting and it only shows the results in the terminal, and doesn't create normal report if you use it with mochawesome reporting for example.
Best Regards
The text was updated successfully, but these errors were encountered: