Helm version upgrade testing harness

mojaloop / project

Repo to track product development issues for the Mojaloop project.

Other

23 stars 15 forks source link

Helm version upgrade testing harness #1403

Open lewisdaly opened 4 years ago

lewisdaly commented 4 years ago

Goal:

As a QA/Test engineer, I want to be able to catch bugs and issues when upgrading from one Mojaloop version to another so I can ensure a reliable product for Hub Operators.

Tasks:

[ ] TBD [ @? ]

Acceptance Criteria:

[ ] Designs are up-to date
[ ] Unit Tests pass
[ ] Integration Tests pass
[ ] Code Style & Coverage meets standards
[ ] Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
[ ] TBD

Pull Requests:

[ ] TBD

Follow-up:

Dependencies:

Accountability:

Owner: TBC
QA/Review: TBC

lewisdaly commented 4 years ago

Outside of scope for now, but might be nice to have in the future.

lewisdaly commented 4 years ago

I feel like this still might be out of scope for our PI, but I did see the "Matrix Jobs" feature on CircleCI, which we could use to regularly test upgrades between all helm releases:

https://circleci.com/blog/circleci-matrix-jobs/

With matrix jobs, we could specify an array of "starting" helm releases: [ "v8.7.0", "v8.8.0", "v9.2.0"]

and ending helm releases: ["v8.8.0", "v9.2.0", "v10.1.0"]

And CircleCI can run every combination of upgrades.