Usage with parallel test runs about cypress-mochawesome-reporter HOT 9 CLOSED

Released in v3.6.0 🥳

from cypress-mochawesome-reporter.

I never tried to use this reporter in parallel mode, but I don't think it would work.
Somehow the reporter needs to fetch the result files from each node and combine them, which is currently not implemented.

from cypress-mochawesome-reporter.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

from cypress-mochawesome-reporter.

I never tried to use this reporter in parallel mode, but I don't think it would work. Somehow the reporter needs to fetch the result files from each node and combine them, which is currently not implemented.

https://www.npmjs.com/package/cypress-parallel runs on the same machine, not on different nodes, and is actually quite interesting to help with basic parallel execution.

I've been able to set up everything to get the json files for each threads. If I run only 1 thread, the whole process works fine. The only issue is by using multiple threads, the first one to finish will trigger the after:run event and will build the report.

By disabling the events I get to a point where I have all json files, but I couldn't figure out how to manually ask to cypress mochawesome report to build the report. That would be the missing piece to make it works. But it may be out of scope for this project as it tries to be a simple solution for good reporting.

from cypress-mochawesome-reporter.

@lems3 can you please provide a simple repo with what you achieved so far?
I may have a solution, but I would like to use an example so I would have something to work on

from cypress-mochawesome-reporter.

I quickly built an example here based on our internal repo : https://github.com/PremierTechDigital/cypress-parallel-report

This is mostly a set of commands with the proper configuration to achieve the result "by hand" instead of using hooks and events in cypress directly. This way, we can be sure that all tests are done before compiling results.

So we're not going trough cypress-mochawesome-reporter to build our report. As cypress-parallel doesn't seems to have any way to properly follow all threads, we went back on doing things "manually".

from cypress-mochawesome-reporter.

The repo and the steps helped me a LOT, thanks.

Please download this reporter 3.6.0-rc.0 version and then follow the steps here

Let me know if it worked for you and if you have any comments/suggestions about the solution.

If everything is okay, I will write more documentation and publish this version.

from cypress-mochawesome-reporter.

@LironEr I just tested out your version and it does work as expected. I was able to get a single report when running tests in parallel. Thanks!
I also noticed that when running your version, I get this error Some test suites likely terminated without passing on results, exit with error

Upon investigation, I can confirm that this happens due to the excludeSpecPattern in the cypress config. We do have 6 tests that have been excluded. It might be better to not worry about the tests that have been excluded to avoid this error/warning?

from cypress-mochawesome-reporter.

Hey @sidsalunke, I am glad to hear this version is working as expected (:
I will release v3.6.0 soon, probably without changes.

As for the issue you noticed, I'm not sure if it's a cypress, cypress-parallel, or this reporter problem.
if you want you can create a repo with the problem and steps to reproduce the issue so I try to have a look.

from cypress-mochawesome-reporter.