LivelyKernel / LivelyKernel/ContextJS
Optimize Travis build matrix
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
When #14 is merged, we will have three builds per push/PR, for the node versions 4, 5, and the latest. But all of them run the karma browser tests, which is nonesense. Ideally, we would have those three builds running the tests only for node (using mocha) and either
- one additional build that tests all browsers (using karma), or
- multiple additional builds that each run tests for exactly one browser
Contributor guide
No contributing guide indexed for this repository
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 locating the Travis CI configuration and reviewing the existing Node versions, Mocha tests, and Karma browser-test commands. Separate the Node-only builds from the browser-test build or builds, then verify that pushes and pull requests still run the intended test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100