-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a new upgrade test case #4141
base: v3.x/staging
Are you sure you want to change the base?
Add a new upgrade test case #4141
Conversation
Signed-off-by: MarkAckert <[email protected]>
build 6775 SUCCEEDED. |
Test workflow 5961 is started. |
Test workflow 5984 is started. |
build 6867 SUCCEEDED. |
Test workflow 6033 is started. |
build 6882 SUCCEEDED. |
build 6922 SUCCEEDED. |
Address #3315 in part.
Zowe upgrade tests naturally involve many different scenarios - across major version boundaries, from minor versions to other minor versions, with certain features or components enabled, with other configuration settings present in zowe.yaml, such certificate configuration, and any combination of these scenarios.
This PR is the simplest case - from a base FMID (3.0) to the latest PTF available (current build). Our existing PTF tests already covered similar ground, so this test does two things differently to try and capture real world migrations:
This should capture errors introduced by changes to the zowe.yaml files and schemas at minimum.
Still to be researched: