You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I've been using this as the basis for a project using cra and crna.
Using the workspace_example provided running yarn test on the native project doesn't work (pretty obvious as it sitl points to ./node_modules/jest/.bin/jest.js which is now in the parent directory.
pointing to the jest file in the parent directory doesn't fix the issue as jest-expo preset is still using the native directory as it's root to find other modules.
Next level of fixing is to change the rootDir in jest. in the end I had to add the following lines to the package.json jest config.
the roots are needed such that it doesn't try and run tests in all folders from the workspace but can still find node modules, however it then can't interpret es6 things anymore. This is where I'm stuck.
The text was updated successfully, but these errors were encountered:
Smtih
changed the title
Yarn test does not work
Yarn test does not work in native
Feb 8, 2018
I made a PR to fix web & native tests: #15
The main "tricks" was to move the native/.babelrc to the root folder (need documentation for that) + update the jest version on native side
So I've been using this as the basis for a project using cra and crna.
Using the workspace_example provided running yarn test on the native project doesn't work (pretty obvious as it sitl points to ./node_modules/jest/.bin/jest.js which is now in the parent directory.
pointing to the jest file in the parent directory doesn't fix the issue as jest-expo preset is still using the native directory as it's root to find other modules.
Next level of fixing is to change the rootDir in jest. in the end I had to add the following lines to the package.json jest config.
the roots are needed such that it doesn't try and run tests in all folders from the workspace but can still find node modules, however it then can't interpret es6 things anymore. This is where I'm stuck.
The text was updated successfully, but these errors were encountered: