Open Eddasol opened 1 year ago
This would be very useful for https://github.com/equinor/flotilla/pull/894 and issue #871 in general
Would it be an idea to have a mission with a specific ID or a certain step that will cause isar-robot to send and error back or mark mission as failed?
Or make isar-robot configurable to always succeed or always fail, and run one of each instances in dev
Will solve this using the Mission.name
attribute to decide if a mission should fail some tasks, by reporting step.status = StepStatus.Failed
Can this be tested with an integration test from ISAR?
Offline state to be introduced in https://github.com/orgs/equinor/projects/85/views/4?pane=issue&itemId=56783224
This issue has automatically been marked as stale as there has been no activity for 60 days.
Get isar-robot to fail some task such that testing through isar-robot will touch larger parts of the code and to allow for testing of failure behaviour.
One option is to use environment variables to decide if it should fail or not.
Some different types of isar-robot that could have different behaviour:
Prerequisite