Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

Set up TravisCI, codecov #31

Open
JohnStrunk opened this issue Jul 3, 2018 · 1 comment
Open

Set up TravisCI, codecov #31

JohnStrunk opened this issue Jul 3, 2018 · 1 comment
Labels
feature New feature or request GCS/beta0

Comments

@JohnStrunk
Copy link
Member

Describe the feature you'd like to have.
Each commit/PR should be checked via Travis.

  • Run linters
  • Run unit tests

What is the value to the end user? (why is it a priority?)
Having linting and unit tests provide a minimum level of assurance for new code submissions, helping to keep quality high.

How will we know we have a good solution? (acceptance criteria)
Each Commit and PR should be checked:

  • linting of all code and docs (if it's a structured file, we should lint it)
  • Run all unit tests
  • Integrate w/ codecov to ensure coverage of unit tests remains acceptable

Additional context
Child of #5

@JohnStrunk JohnStrunk added the feature New feature or request label Jul 3, 2018
@JohnStrunk JohnStrunk added this to the 0.9 milestone Jul 3, 2018
@JohnStrunk JohnStrunk mentioned this issue Jul 3, 2018
2 tasks
@JohnStrunk JohnStrunk added the ready This item is ready for work label Jul 11, 2018
@JohnStrunk JohnStrunk self-assigned this Jul 11, 2018
@JohnStrunk
Copy link
Member Author

Moving this back to the backlog to be picked up again once we have code.

@JohnStrunk JohnStrunk removed their assignment Jul 12, 2018
@JohnStrunk JohnStrunk removed the ready This item is ready for work label Jul 12, 2018
@JohnStrunk JohnStrunk modified the milestones: 0.9, GCS-1.0 Sep 24, 2018
@JohnStrunk JohnStrunk removed this from the GCS-1.0 milestone Oct 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature New feature or request GCS/beta0
Projects
None yet
Development

No branches or pull requests

1 participant