Exporting the test failure reason in VDTESTING_FAILURE_REASON #86
Conversation
This file contains 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.
Checklist
step.ymlandREADME.mdis updated with the changes (if needed)Version
Requires a MAJOR/MINOR/PATCH version update
Context
This PR changes the step to export
VDTESTING_FAILURE_REASONwhen the UI test fails. This allows the developers to use the environment variable to utilise the failure reason in the next steps. e.g. They can put the failure reason in the slack messages to identify failure the reasons easily. Or retrigger workflow if the test failed because of recoverable reason (i.e. Crashed).Changes
Updated
main.goto exportVDTESTING_FAILURE_REASONusing envman with the failure reason (which is the same as what we display in the outcome summary.)Investigation details
No alternative solutions were considered.
Decisions