'npm run test' not working on windows

[nyrosmith]

Win 10 x64 node: 4.4.7. I have also tried with node 6.3.1. (current)

It seems that mocha freezes when running the tests. All I get is

webpack-validator@ test E:\webpack-validator
cross-env NODE_ENV=test mocha "src/**/*.test.js"
  ......................................

and then it hangs forever. I am really not sure if it is a problem in the scripts or mocha itself. Help would be really appreciated...

[kentcdodds]

Hmmm... I got it working (on my mac) without trouble. Maybe there's a specific test that has problems. Could you see if you can find the hanging test?

[nyrosmith]

Need to do binary search to detect the potential test. Let me see if I find something suspicious.

[nyrosmith]

I could tackle the problem down to this line Nothing after const nodeModuleFolder = findNodeModules({ cwd: path_, relative: false })[0] executes. The problematic test whith the problem causing config is this one

My approach is to adjust the testConfigs to provide valid absolute paths if ENV === windows. Any thoughts about this solution @kentcdodds @jonathanewerner ?

[kentcdodds]

I'd love to see it 👍

[nyrosmith]

After some hours of investigation I found the following possible solution.

• create valid absolute paths in our tests depending on current OS
• Fix query if it's an absolute path (#131)
• split passing & non passing configs in different folders (per OS)
• run these test webpack-configs tests for the current OS only

This is a bigger change as I expected and it might have some tradeoffs, but otherwise I would not be able to contribute any longer which I really like...

I don't want to make that changes until you all are ok with that @kentcdodds @bebraw @jonathanewerner

[bebraw]

Fine by me. If you can encapsulate the path bits somewhere, that would be great.

[kentcdodds]

:shipit: 😄

[jonathanglasmeyer]

Fine by me. If you can encapsulate the path bits somewhere, that would be great.

Yea, let's extract this as test/mock/absolutePath or something.