Skyscanner/turbolift

Basic integration testing

Opened this issue · 0 comments

We have lots of unit tests, but we can't assert whether turbolift does what it's supposed to do.

We would want to have minimal CI integration testing with the following:

  • basic clone
  • change something
  • commit
  • push

With basic validation steps like making sure the PR contains elements from the README file.

Potential issues and leads:

  • how do we not overflow github with PRs at every run
  • do we create a set of repos and keep it, or do we create a set for each run?
  • how does security play a role in this