influxdata / influxdata/influx-cli
Design our e2e testing strategy
Open
Nobody has claimed this yet.
testing
- Dominant language
- Go
- Stars
- 75
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Questions to answer:
- When do we want to run e2e tests?
- On every PR?
- As a nightly job?
- Before releases?
- Which host systems do we want to e2e test?
- linux/amd64?
- linux/arm64?
- darwin/amd64?
- windows/amd64?
- How can we e2e test against InfluxDB OSS?
- How many versions of InfluxDB OSS to we want to e2e test against?
- Do we need to run and OSS instance within our CI pipeline, or can we host one for testing?
- How can we e2e test against InfluxDB Cloud?
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
The issue provides no file, test, or CI entry point to start from; first map the repository's existing test and CI configuration. Resolve the listed scheduling, host, InfluxDB OSS, and InfluxDB Cloud questions, then document an agreed end-to-end testing strategy and its implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, cli, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100