-
Notifications
You must be signed in to change notification settings - Fork 674
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
TestCafe on Windows fails with exit code 1 #4665
TestCafe on Windows fails with exit code 1 #4665
Comments
Thank you for your report. Could you please try to run the following command in your terminal and share results here:
|
Thanks for your response. Here is the output of the command:
|
The output looks pretty normal. I have to prepare a debug build that will display a hidden PowerShell |
Sure, no problem. |
Thank you for your patience. Please install the debug build by running
or
and share the output. |
here's the command output:
|
Thank you for the provided output. Unfortunately, this error indicates a problem with the debug build's package. Could you please install the second build by using |
Ok, done. But it does not look like it generated a logfile this time:
|
Thank you for your cooperation. I can reproduce the issue now. It is caused by a combination of enabled PowerShell Strict Mode in your PowerShell profile, this escape sequence in a template string in We need to fix the template string and avoid loading user profiles for PowerShell. As a workaround, you can try to locate the |
Hi @AndreyBelym your workaround is doing the trick for now, but do you have any update on this and a potential fix? All I know is that the latest version 1.8.1 that has been released since I raised this issue has not brought any improvements. |
Unfortunately, we don't have time to fix it and include it into the upcoming release (which is expected to be |
Hi @AndreyBelym I noticed that v1.8.3 has now been released. I presume the issue has not been addressed, given that it has not been closed? |
@Holger2233 yes, we will close the issue once it's fixed. |
Hi @AlexKamaev and @AndreyBelym I just installed the latest version 1.8.5 and re-enabled PS strict mode again (which was disabled as temporary workaround), but does not look like the issue is fixed yet. Testcafe still does not run and fails with the error below, while working fine with PS Strict mode disabled.
|
Hi, the fix was merged into our codebase, but we need to publish a new release. The fix will be included in |
Thank you for your patience. I want to inform that |
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
1 similar comment
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
Following up on the previous issue #4646 with TestCafe on Windows, the new TestCafe version 1.8.0. does now fail with a different error:
What is your Test Scenario?
just running testcafe
What is the Current behavior?
testcafe fails with exit code 1 error
What is the Expected behavior?
testcafe runs successfully with any valid test and command options
What is your web application and your TestCafe test code?
n/a
Steps to Reproduce:
Install TestCafe v1.8.0 on Windows as per instructions https://devexpress.github.io/testcafe/documentation/using-testcafe/installing-testcafe.html#local-installation
run testcafe -b command
Result: Running testcafe with any option that involves a browser results in the following error. Only exceptions are testcafe -h and testcafe -v:
Your Environment details:
testcafe version: 1.8.0
node.js version: 13.6.0 (64bit)
command-line arguments: e.g.
testcafe -b
ortestcafe chrome ./test.js
platform and version: Windows 10.0.18363
npm version: 6.13.6
The text was updated successfully, but these errors were encountered: