This PR changes the step to export VDTESTING_FAILURE_REASON when 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.go to export VDTESTING_FAILURE_REASON using envman with the failure reason (which is the same as what we display in the outcome summary.)
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