Start e2e/integration testing functionality. #507
Conversation
The test suite will install the solr operator via the helm chart. The first pass will not be for release testing yet.
90474ff to
6191f4b
Compare
|
Ok smoketester usage is now completely covered by the e2e tests. This should be pretty close to merging in early january once we have some other eyes on it! Btw #511 is required for the tests to pass, so we should decide on that before merging this in. |
|
Ok, big win. Much like the solr tests, the e2e tests are now completely reproducable with all possible inputs (random seed, operator/solr image, kubernetes version, etc), and accept easy filtering. On test failure each individual test will also output a command to reproduce the test failure.
This should be ported to the unit tests in a separate PR, because its an awesome feature and very much missing from the operator tests. We are reaching the finish line here. I am going to document the tests and clean up |
|
Ok I don't think Github Action runners have the resources to run the e2e tests, so we will have to disable those for now. We can have them run in Jenkins instead for now. |
|
I think this is ready to go and plan to commit it early next week! |
Resolves #134
This is the first of hopefully many integration testing tickets, mostly to build the start of a framework so that other work can be done iteratively.
Goals/Progress:
Future Goals, not required for this ticket: