influx-cli icon indicating copy to clipboard operation
influx-cli copied to clipboard
verified publisher icon influxdata

Design our e2e testing strategy

Open danxmoran opened this issue 4 years ago • 2 comments

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?

danxmoran avatar Apr 12 '21 17:04 danxmoran

We might be able to use the testscript package for this.

danxmoran avatar May 26 '21 18:05 danxmoran

BATS and expect might also be useful. Some discussion about combining the two to test Go CLIs is here.

danxmoran avatar Jun 10 '21 13:06 danxmoran