Run tests in Windows OS - #22
Conversation
There was a problem hiding this comment.
At least on Travis, npm needs to be upgraded so that things work with dependencies using ^. Will that be an issue on AppVeyor as well?
There was a problem hiding this comment.
Yes, on AppVeyor npm also needs to be upgraded.
|
I've set up AppVeyor to run on all branches. If you push a new commit, I assume a build will be triggered and both AppVeyor and Travis should report on the commit status. Would you mind pushing a new version of 9d70eca so we could test? Or if things should work another way, let me know. |
|
I tried to add commit to run tests in AppVeyor. It started — https://ci.appveyor.com/project/tschaub/mock-fs/build/3. |
|
With Node 0.12 out, I'm happy to drop 0.8 from the Travis and AppVeyor runs if getting the right |
|
Build with 0.8 was success: https://ci.appveyor.com/project/tschaub/mock-fs/build/5/job/dmff8tnvgmna153d At the moment AppVeyor not support Node@0.12: https://ci.appveyor.com/project/tschaub/mock-fs/build/4/job/g4s01f1psukunnja |
|
Nice. Not fast, but free is good. Thanks for the work on this @andrewblond. |
To run tests in Windows OS on every Pull Request or commit as well as using the Travis need use AppVeyor.
For this need to add configuration file
appveyor.ymland addmock-fsto your projects in AppVeyor.More read in docs.