steps-virtual-device-testing-for-android icon indicating copy to clipboard operation
steps-virtual-device-testing-for-android copied to clipboard

Published 20 hours ago • verified publisher icon bitrise-steplib

Exporting the test failure reason in VDTESTING_FAILURE_REASON

Open kevalpatel2106 opened this issue 2 years ago • 0 comments

Checklist

  • [x] I've read and followed the Contribution Guidelines
  • [x] step.yml and README.md is updated with the changes (if needed)

Version

Requires a MAJOR/MINOR/PATCH version update

Context

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.)

Investigation details

No alternative solutions were considered.

Decisions

kevalpatel2106 avatar Mar 10 '23 17:03 kevalpatel2106