NativeScript / NativeScript/nativescript-cli
Running tns test android does not detect tests and is stuck in `test: loading; `
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Environment
- CLI: 8.1.4
- karma: 6.3.7
- karma-jasmine: 4.0.1
- karma-webpack: 5.0.0
- karma-nativescript-launcher: ~2.9.0
Describe the bug
I initalized tests using tns test init using jasmine. After running tns test android, in the browser the header shows test: loading and it doesn't appear to load any test files in the network tab. The mobile app that's launched on my emulator shows no tests. I did not make any modifications to the version of the dependencies or to the generated karma.conf.js. There were no errors in the logs.
To Reproduce
Run tns test init and select jasmine
Run tns test android, it launches the app with no tests displayed. In the browser, it displays test:loading
Expected behavior
My unit tests to be displayed and their status.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with tns test init, selecting Jasmine, and running tns test android; inspect the generated karma.conf.js and the browser network activity while the emulator launches. Compare the expected test loading flow with the observed test: loading state, and consider the issue done when the initialized unit tests appear in the browser and emulator with their status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- cli, mobile, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100