-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
tns test
command cannot work if the source is not in src
directory
#5070
Comments
Two different webpack compilations are started on `tns test` command - the one from `karma-webpack` and the second one from `nativescript-dev-webpack`. As the karma's webpack doesn't provide appPath to the env and there is a hardcoded `appPath` inside `webpack.config.js` (to `src` for example), it works only with that hardcoded path. Rel to: #5070
Two different webpack compilations are started on `tns test` command - the one from `karma-webpack` and the second one from `nativescript-dev-webpack`. As the karma's webpack doesn't provide appPath to the env and there is a hardcoded `appPath` inside `webpack.config.js` (to `src` for example), it works only with that hardcoded path. Rel to: #5070
Is this change available with a "next" version of the CLI on npm? When will it be available in latest? |
Hey @jevenson, The change is available in the |
Actually just updating CLI will not fix the problem if you have already executed nativescript-cli/resources/test/karma.conf.js Line 102 in e75acf8
|
Environment
Provide version numbers for the following components (information can be retrieved by running
tns info
in your project folder or by inspecting thepackage.json
of the project):Describe the bug
Currently
tns test
command throws the following error in case when source code is not insrc
directory:To Reproduce
There are 2 options to reproduce the issue:
Option 1:
https://github.com/NativeScript/sample-Groceries
npm i
&&tns test ios
Option 2:
src
tosrc1
appPath
tosrc1
insidensconfig.json
tns test ios
Expected behavior
The unit tests should be successfully executed.
The text was updated successfully, but these errors were encountered: