Integration Tests
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
@jenningsanderson should we integrate https://github.com/mapbox/osm-wayback/tree/master/test into Travis?
Can we make repeatable tests out of those?
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 inspecting the existing tests in test/ and the repository's Travis configuration. Determine how those tests can run repeatably in CI; done means the integration tests execute reliably through Travis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100