Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Going crazy with --watch

See original GitHub issue

If i add --watch flag, the reporter is going crazy. It looks like he is doing all tests multiple times and adds and removes the css several times. Sometimes they are missing at the end of the crazy-going-session.

Issue Analytics

State:
Created 7 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

adamgrubercommented, Feb 16, 2017

This is fixed with mochawesome-report-generator@1.0.8. Assets only get copied once and no longer trigger infinite test re-runs.

1reaction

adamgrubercommented, Feb 12, 2017

Did some research on this. The issue comes from how mocha determines what files to watch. Mocha will watch all .js files inside cwd. If it’s the first time running tests with mochawesome you’re fine but every time after mocha will find the app.js file created by mochawesome and add it to the list of watched files. Since that file gets created each time the reporter runs, mocha picks it up as changed and runs the test again putting the whole process into an endless loop. Unfortunately mocha does not currently offer options to watch or ignore certain files.

As a workaround, you can run mochawesome with the inlineAssets option set to true. This prevents the app.js file from being created since all assets get inlined into the report HTML file.

I am going to look into changing mochawesome so it won’t recreate the assets folder if it already exists.