NativeScript / NativeScript/nativescript-cli
Auto-exit after `tns test` completes and allow for console output collection
Open
Nobody has claimed this yet.
feature
unit testing
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
The currently recommended approach to running tns test in a CI environment is to use the --justlaunch switch, so that tns exits after the test run completes.
- We need a way to run without
--justlaunch, so we showconsole.logand other output to the user and let CI systems collect it in their build logs. - We also need a
--timeoutparameter that will kill the test run if it doesn't complete in X minutes/seconds.
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 with the tns test command and trace the existing --justlaunch behavior. Define completion by preserving console output for CI, adding a --timeout parameter, and ending the test run automatically when it completes or times out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100