-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Framework needs to help test authors understand how to pass state between steps #66
Comments
It's a real problem, we need to find a solution for this. An example:
In this case I wanted to compose the Address retrieval (which might be a stepfn itself) with eventshub.Install, propagating the address. It would be nice to have a solution that just compose these two steps together |
OK brain wave.... It was my intention that the requirement timing would let you block until it passes while setup phases were happening so the testing phase works. BUT! what if we change how Requirement works, and it gets paired with Setup as a prereq for running Setups. The setup phase is optional, example:
How to know a Require is paired with a Setup? Match the name of the step. ok this does not solve the problem at hand, so I think we also introduce a config store that can be blocking:
feature.Feature looks like this now
But we could change it to be:
and config.Store is something like
|
Then steps have two places (context &| config) to get things from and they're both untyped and have loose contracts. |
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen |
I wonder if step function should change to return a potentially new context ie. |
One issue has the testing framework makes it had to pass state between components. How do we solve this? Is it a real problem?
The text was updated successfully, but these errors were encountered: