You need to sign in or sign up before continuing.
Improve Outputs by adding to OutputAttribute
New feature request as discussed with Rolf and Asger.
- Make OutputAttribute able to specify when the output is available.
-
Automatic <- After run is used if no defer is specified by the user. Otherwise after defer is default.(Rolf 28 Jan 2021) This is actually the same as AfterChildDefer. - AfterChildDefer <- Currently the default behavior
- AfterRun
- AfterDefer
- Property/Event + Name (Advanced)
-
- Support the wait in the new Input/Output system (
- Use OutputAttribute(..AfterChildDefer) on TestStep.Verdict.
I also attached the related email discussion related to this enhancement request: [[Deleted]]
(Rolf 28 Jan 2021) Testing scenarios:
- sequential steps wait for sibling output.
- parallel steps wait for sibling output.
Here I detected some issues that can occur if one step needs anothers step output, but I think in this case the user can design the test plan around it. It looks like this:
- Parallel Step
- Output Step
- Input Step
In this case input needs to wait for output to complete, but when Input starts, output might not have been started yet or it might have completed already. it is really impossible to say from the perspective of input step. The question then become, is this important? If input step depends on the result of output step, why not just place them in sequence?
Edited by Rolf Madsen