-
-
Notifications
You must be signed in to change notification settings - Fork 197
The test android command fails to run tests #1636
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
Even I'm facing the same issue (on TNS 2.0). Any updates on this? Will there be a fix for this, if the root cause is known. Thank you. |
I have the same problem, version 2.0.0, here is a part of crash message on the device:
|
+1 I also had the same problem:
|
+1 I have the same problem.
|
I'm in version 2.0.1 and still have the problem. The workaround works though. |
Thanks, guys! Hey @rosen-vladimirov, @hdeshev, @vakrilov, do you have any idea about this issue? I still reproduce it rarely with our master branches, in particular: CLI - 2.1.0-734 |
Yup, same problem. Workaround gives some error about tns-karma. |
First call to `tns test <platform>` always fails as the file with Karma configuration is not sent to device. The reason is that it's craeted in `node_modules/unit-test-runner` after the project is prepared. The second execution of the command will include the file, but it may not be correct. It's regenerated, but again after the project is prepared. Fix the `test-execution-service` to prepare the project after the configuration file is created. Fixes #1636 and possibly #2016 Fixes the problem in Travis builds that console hangs and travis builds never end.
Steps to reproduce:
|
tns test android
fails with _com.tns.NativeScriptException: Failed to find module: "./config", relative to: /app/tns_modules/nativescript-unit-test-runner_.Steps to reproduce:
package.json:
Output:
Workaround:
Rerun the
tns test android
command.The text was updated successfully, but these errors were encountered: