-
Notifications
You must be signed in to change notification settings - Fork 169
unable to run qa env #57
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
Comments
Hi @prajyot7 . I will have a look into this issue. Are you running this as it is or have you modified something? |
Hi @akshayp7 |
@kwiatek91 : I just checked in my windows Machine I was able to launch it. Please try command |
Can you also please check if other commands are working for you because the above command will run entire tests.. |
same thing @prajyot7 did you found any solution are you working on Windows/Linux/Mac? |
@prajyot7 : I have checked on Windows os. It's working on Ubuntu Linux as well I had checked. Mac I didn't get opportunity to check |
so this looks like system problem (project setup) on macos (other project works good, but maybe there is some problem in configuration to be honest i don't have enaught knowledge right now from TS / Playwright to find what cause the problem, but definitely it is a problem with parametrization) |
@prajyot7 , @kwiatek91 : For MAC i think cross-env library works fine. I had added this in my project earlier but then later i removed cross-env package and tried using internal ENV provided by ts. You can check out my earlier releasewhere I have used cross-env Checkout my 1.2.0 release. |
Did you get a change to use cross-env . Did issue get resolved |
Any updates on the issue @prajyot7 @kwiatek91 ? |
Same issue I'm facing on Mac |
@Akhilesh7057 : please try cross-env library it's with 1.2.0 release and let me know if it works. Or I had same issue while creating docker container so I defines environment variable in file itself. You can take abloom at the docker file and docker run command. |
Solution for MAC-users : Before running the test execution command please run the below command |
@yashlohakare-certa thank you for your help and support. Can anyone else confirm that this solution is working for you. |
Closing this issue as solve. Please reopen if you face the same even after using export npm_config_ENV="qa" command |
Hi Guys. If you are using VS code please try the below suggestion on your MAC machines |
The text was updated successfully, but these errors were encountered: