Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Classify whether a failure is an assertion-choice problem, tolerance problem, or real workflow-output regression.
- Trigger
- When Planemo reports output assertion failures or generated tests are too strict/too weak.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Decide whether a proposed debug fix aligns with accepted IWC testing shortcuts or masks a real failure.
- Trigger
- When debugging suggests weakening assertions, widening deltas, switching to existence checks, or changing output labels.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Diagnose collection shape, mapping, reduction, and element-identifier mismatches in failed Galaxy runs.
- Trigger
- When a failing output is a collection, a mapped output, or an unexpectedly nested/flattened structure.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Trace collection output failures back to possibly lossy operator translations.
- Trigger
- When debugging wrong nesting, missing elements, branch merges, bad joins, or gather/reduction mismatches.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Interpret Galaxy job-level failure evidence including stdio rules, exit code, job messages, and output dataset state.
- Trigger
- When a failed workflow test includes errored jobs, tool stderr/stdout, non-zero exit codes, or red output datasets.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Interpret Galaxy invocation-level failure evidence including invocation state, structured messages, and step job summaries.
- Trigger
- When a failed workflow test has invocation failure, missing workflow outputs, cancelled/paused steps, subworkflow failures, or collection population errors.
Background synthesis loaded by explicit progressive-disclosure metadata.
- Purpose
- Locate which Planemo artifact or Galaxy API surface preserves the failure evidence.
- Trigger
- When Planemo output is ambiguous, structured test JSON is available, or rerunning can be avoided by inspecting an existing invocation.