This is some thing many of you have been asking about so I wanted to make sure all were aware, but also get some feedback.
Our previous input/output structure was based around a few things.
IInput<>type in one Test Step
[Output]attribute in another Test Step
Then based on the Types the Editor would allow for connection. This had a few limitations:
- Everything needed to be decided at Dev time (what will except Inputs and what will create Outputs)
- A Setting needed to choose being accepting an Input OR being manually set, it could not be both.
- If lots of inputs and outputs were used, the dropdown of options could be very large.
As of 9.10 we have fundamentally reworked this. The previous use case still exists for the very closely related steps, but in the more open ended and flexible case, we have pushed most of the up to the UI.
Output attribute is still needed. In general, we encourage this to be used more. Anything that COULD be used, should be an output.
From there, the outputs can be mapped to inputs in code. You can see that in this gif:
I’m interested to hear what people think. Does this enable more use cases? Anything we still need to add?