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
constsfn=newStepFunction<undefined,string>(()=>{return"hello";});constresult=sfn();// invalid - what does it mean to start a long running execution locally?
consteb=newEventBus();constsfn=newExpressionStepFunction<undefined,string>(()=>{eb();});constresult=sfn();// fails, eb() does not support standalone;
Mocked Nested
consteb=newEventBus();constsfn=newExpressionStepFunction<undefined,string>(()=>{eb();});mockIntegration(eb,()=>{});constresult=sfn();// success! eb is mocked
The text was updated successfully, but these errors were encountered:
This is a longer term goal but I believe we can offer a similar experience for non-express step functions. Even though they don't return synchronously, we can expose an integration for DescribeExecution. Users could then write async tests locally by polling for the result.
We could do similar things with queues and event buses.
Integrations should be executable outside of resource closures in certain cases for the following use cases:
Testing
Using logic during synthesis
Create
standalone
integration typeImplement
standalone
forFail for all other uses
Support nested standalone integrations
Mock integrations
Valid Use:
Invalid Use:
Nested Use
Invalid nested
Mocked Nested
The text was updated successfully, but these errors were encountered: