You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the above behavior was because of missing babel env config. But even if I add that unit test works fine but in full app mode, the test command is getting stuck at building for web.browser . When enabled verbose logging, it is stuck after DONE 2 processing files with less (for target web.browser) took 38
Hello.
If you correctly setup the environment, the instrumentation of your code is done by babel and I don't think it can freeze like that during the process. Try to setup a small reproducible environment to setup coverage and you will discover by yourself what's wrong with your app. Don't forget there is exemple available to setup coverage.
Good luck, feel free to continue to ask questions if you have more stuff
Expected Behavior
On opening localhost:3000/coverage, it should show coverage
Current Behavior
On localhost:3000/coverage, it says no coverage has been reported but all tests have run successfully.
Also for unit tests, coverage has been added but there is no css file which makes it very hard to figure out the lines covered
Your Environment
The text was updated successfully, but these errors were encountered: