16.3 Script Failures [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 16.3 Script Failures ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:16-exception-handling:start | Return to Exception Handling ]]

Scripts should fail clearly when required conditions are not met. A script should not continue after a missing prerequisite, invalid argument, missing input file, invalid Configuration, failed generation step, failed build step, failed runtime startup, or failed validation step unless the script explicitly supports partial completion.

Script failure handling should include:

  - Clear error messages.
  - Meaningful non-zero exit codes.
  - Identification of the failed check or operation.
  - Identification of the expected input, tool, path, or condition.
  - Guidance on what the user should inspect next.
  - Preservation of useful logs or intermediate Evidence where practical.
  - Avoidance of destructive cleanup unless explicitly requested.

Scripts should distinguish warnings from failures. A missing optional tool may produce a warning. A missing required tool should cause failure. A failed required build or validation step should cause failure. A script should not return success when a required action fails.

Script failure behavior should align with the script conventions defined in Section 13. Scripts that support CI or acceptance Evidence should produce output that automated tools and reviewers can inspect.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>