influxdata / influxdata/influxdb
Delete TestFluxEndToEnd when new test framework has enough coverage
Open
1.x
area/2.x
area/flux
area/tests
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Flux is moving away from code-generating test cases for use via go, in favor of their new framework driven by `.flux` test files. When the tests packaged in the new framework reach the coverage of the old-style codegen'd test cases, we can delete `TestFluxEndToEnd`.
Contributor guide
Research direction
Start by locating TestFluxEndToEnd and the new framework's tests driven by .flux files. Compare the new framework's coverage with the old code-generated test cases; done means the coverage is sufficient and TestFluxEndToEnd can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100