Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-23156

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

    Details

      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.

        Attachments

          Issue Links

            Activity

            Hide
            krzys 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
            krzys 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:
                krzys Krzysztof Findeisen
                Reporter:
                krzys Krzysztof Findeisen
                Watchers:
                Krzysztof Findeisen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel