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

Unable to run all tests in project #36

Open
svego opened this issue Jul 5, 2019 · 1 comment
Open

Unable to run all tests in project #36

svego opened this issue Jul 5, 2019 · 1 comment

Comments

@svego
Copy link

svego commented Jul 5, 2019

When i use the option 'Run Test(s) in Chrome' on my project directory the testcafe test fails with the following error:

PS C:\Source\mytestdir> cd 'c:\Source\mytestdir'; & 'C:\Program Files\nodejs\node.exe' '--no-deprecation' '--inspect-brk=17323' 'node_modules\testcafe\lib\cli\index.js' 'chrome' 'c:\Source\mytestdir'
Debugger listening on ws://127.0.0.1:17323/a4fc9578-5127-47ff-aa14-2f0348b046e8
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
The "src", "browsers" options from the configuration file will be ignored.
ERROR TypeError: this.precompile is not a function or its return value is not iterable
at TypeScriptTestFileCompiler.compile (C:\Source\mytestdir\node_modules\testcafe\src\compiler\test-file\api-based.js:177:37) at Compiler._getTests (C:\Source\mytestdir\node_modules\testcafe\src\compiler\index.js:87:31) at Compiler._compileTestFiles (C:\Source\mytestdir\node_modules\testcafe\src\compiler\index.js:99:35)

Type "testcafe -h" for help.
Waiting for the debugger to disconnect...

When i manually run the same command but remove the directory specification (so use testcaferc.jsin option) all my tests run normally. The command that works is this:
'C:\Program Files\nodejs\node.exe' '--no-deprecation' '--inspect-brk=17323' 'node_modules\testcafe\lib\cli\index.js' 'chrome'

As a workaround, is it possible to change the behaviour of the command that is used to run my tests?

@AndreyBelym
Copy link

Hello @svego, could you please specify your TestCafe version? Have you tried to run the full command manually? Also, it will be very helpful if you can provide a sample project that can be used to reproduce the issue.

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

No branches or pull requests

2 participants