# Add ways to test a PipelineTask's init inputs/outputs

XMLWordPrintable

## Details

• Type: Improvement
• Status: To Do
• Resolution: Unresolved
• Fix Version/s: None
• Component/s:
• Labels:
• Story Points:
4
• Team:

## Description

DM-22599 created a test framework for validating many parts of a PipelineTask, including its normal inputs and outputs. However, it does not support InitInputs or InitOutputs. Add analogous test methods for these connections.

## Activity

Hide
Krzysztof Findeisen added a comment -

Deferring this until we get some more user experience with the existing code. InitOutputs could probably be handled much like Outputs (see the current assertValidOutput), but I'm not sure about the best way to handle InitInputs. The main thing that can go wrong there is a bug in any optional inputs, or a mismatch between what the config thinks is needed and what the task code assumes.

Show
Krzysztof Findeisen added a comment - Deferring this until we get some more user experience with the existing code. InitOutputs could probably be handled much like Outputs (see the current assertValidOutput), but I'm not sure about the best way to handle InitInputs. The main thing that can go wrong there is a bug in any optional inputs, or a mismatch between what the config thinks is needed and what the task code assumes.

## People

• Assignee:
Krzysztof Findeisen
Reporter:
Krzysztof Findeisen
Watchers:
Krzysztof Findeisen