This repository was archived by the owner on Apr 30, 2020. It is now read-only.
This repository was archived by the owner on Apr 30, 2020. It is now read-only.
Open
Description
Describe the feature you'd like to have.
We need a CI system to ensure master remains healthy as development progresses.
What is the value to the end user? (why is it a priority?)
Having a healthy master means that users don't need to search for a "stable build" to use, and we will be able to release new features faster with higher quality than would otherwise be possible.
How will we know we have a good solution? (acceptance criteria)
- CI system runs against all PRs and master branch
- CI system runs linters
- CI system runs all unit tests
- CI system runs e2e tests
Work items
- Unit testing: Set up TravisCI, codecov #31
- TravisCI: linters, unit tests
- codecov
- E2E testing via CentOS CI - Set up E2E tests on CentosCI #29