Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run tests successfully on Windows #50

Open
kfranqueiro opened this issue May 14, 2018 · 4 comments
Open

Can't run tests successfully on Windows #50

kfranqueiro opened this issue May 14, 2018 · 4 comments

Comments

@kfranqueiro
Copy link

kfranqueiro commented May 14, 2018

When running npm test, an error occurs in the stop script:

> ./test/screenshot/stop.sh

'.' is not recognized as an internal or external command, operable program or batch file.

This might be because ps aux has different output format in MinGW on Windows. (I assume it wouldn't work at all from a standard command prompt.)

@moog16
Copy link

moog16 commented May 14, 2018

I think we get around this with the cross-env package in MDC-Web. I can add that and test on windows.

@lynnmercier
Copy link
Contributor

Steps to reproduce:

Expected behavior

  • local screenshots should pass

Actual behavior

  • local screenshots do not pass (we need to try this again now that we've moved to Docker, but we're pretty sure our documentation does not support Windows users)

@madaz
Copy link
Contributor

madaz commented Feb 13, 2019

PR #662 includes the cross-env and rimraf changes to be able to npm run test:unit

@moog16
Copy link

moog16 commented Feb 13, 2019

@madaz we still need to get screenshot tests to work as well. This specifically references the npm stop/npm start scripts - which are run in a dockerized container. Not sure how our docker container runs on a windows machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants