You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not comprehensive enough since it only tests "latest tag" to current version upgrade path and it doesn't test CRD upgrades (is installing new version of CRDs safe and non-breaking?).
This issue tracks the effort of adding a new test suite which will test operator upgrades.
For example it could test upgrades from a known, predefined list of tags to a a known, predefined list of tags. Additionally this suite would also test installing new CRD versions so that those do not bring breakage.
Acceptance criteria
New testing harness is added which tests upgrades from known operators tags to known operator tags, using a way of deployment closest to the one used by the end users.
As a developer I can be sure that the changes I introduce will not break during upgrades from an older version to the version I'm developping.
The text was updated successfully, but these errors were encountered:
Problem statement
Currently operator has 1 E2E tests which tests the upgrade path
gateway-operator/test/e2e/upgrade_test.go
Lines 30 to 40 in ec5a314
This is not comprehensive enough since it only tests "latest tag" to current version upgrade path and it doesn't test CRD upgrades (is installing new version of CRDs safe and non-breaking?).
This issue tracks the effort of adding a new test suite which will test operator upgrades.
For example it could test upgrades from a known, predefined list of tags to a a known, predefined list of tags. Additionally this suite would also test installing new CRD versions so that those do not bring breakage.
Acceptance criteria
The text was updated successfully, but these errors were encountered: