You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The junit5 assertion components run flows as DynamicTest instances, so you get a flat list of tests in your IDE. You can then use your IDE's interface to rerun individual cases by, e.g.: right-click>run.
This is fine for simple flows, but breaks down a bit for flows with dependencies - your IDE will run the case you want, but it has no notion of the dependency so your test will inevitably fail.
Flow's own test selection facilities deal with this issue by walking the dependency tree and including everything that is required for the desired flow, but it'd be nice to improve the IDE integration even a little bit.
I can't think of a way to deal with arbitrary dependencies, but we can easily improve things for flows in a chain (which are extremely likely to have dependencies on each other). The execution-order behaviour will produce a flat list of flows, and flows in a chain are guaranteed to be lumped together in that list. We can therefore easily package those chained flows into their own DynamicContainer instance.
This should be displayed in the IDE as a subtree, so if you want to rerun something in a chain you've got a single thing that you can right-click on.
The text was updated successfully, but these errors were encountered:
The junit5 assertion components run flows as DynamicTest instances, so you get a flat list of tests in your IDE. You can then use your IDE's interface to rerun individual cases by, e.g.: right-click>run.
This is fine for simple flows, but breaks down a bit for flows with dependencies - your IDE will run the case you want, but it has no notion of the dependency so your test will inevitably fail.
Flow's own test selection facilities deal with this issue by walking the dependency tree and including everything that is required for the desired flow, but it'd be nice to improve the IDE integration even a little bit.
I can't think of a way to deal with arbitrary dependencies, but we can easily improve things for flows in a chain (which are extremely likely to have dependencies on each other). The execution-order behaviour will produce a flat list of flows, and flows in a chain are guaranteed to be lumped together in that list. We can therefore easily package those chained flows into their own DynamicContainer instance.
This should be displayed in the IDE as a subtree, so if you want to rerun something in a chain you've got a single thing that you can right-click on.
The text was updated successfully, but these errors were encountered: