[TECHNICAL] Add workflow to test upgrade from "latest" to current#4663
Merged
[TECHNICAL] Add workflow to test upgrade from "latest" to current#4663
Conversation
547e8a0 to
3249a72
Compare
442409f to
eab3a0f
Compare
5507e59 to
e953479
Compare
6ff5d01 to
ebe1ddf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues
Update testing is required to every release pre-QA stage, to assure that the new build will migrate correctly over the existing version. The current pull request automates such process.
In this first version, this is the process:
latestandcurrentby using a matrix that will run both in parallellatestversioncurrentover thatSettings.For sure, more assertions and checks could be added to have a more accurate testing.
As artifacts:
App:
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA