I noticed this happening when the concurrency was set to something greater than one (default). Not sure why this is happening, but it is probably a race condition. Have not checked the behavior in node, but I have seen it when running in a browser. Also seeing it when wrapping the command using npm test in package.json even with concurrency set to one.
I noticed this happening when the concurrency was set to something greater than one (default). Not sure why this is happening, but it is probably a race condition. Have not checked the behavior in node, but I have seen it when running in a browser. Also seeing it when wrapping the command using
npm testinpackage.jsoneven with concurrency set to one.