Skip to content
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

Section: AWS Services / Step Function #24

Open
4 tasks
szikszail opened this issue Oct 13, 2022 · 5 comments · May be fixed by #35
Open
4 tasks

Section: AWS Services / Step Function #24

szikszail opened this issue Oct 13, 2022 · 5 comments · May be fixed by #35
Assignees
Labels
documentation Improvements or additions to documentation section:service

Comments

@szikszail szikszail added documentation Improvements or additions to documentation section:service labels Oct 13, 2022
@szikszail szikszail changed the title Write section: AWS Services / Step Function Section: AWS Services / Step Function Oct 14, 2022
@szikszail szikszail self-assigned this Oct 27, 2022
@szikszail szikszail moved this from Todo to In Progress in Idea Pool - AWS Testing Oct 27, 2022
@szikszail szikszail linked a pull request Oct 28, 2022 that will close this issue
@szikszail
Copy link
Member Author

@szikszail szikszail assigned sorosz89 and kornel-filep and unassigned szikszail May 2, 2023
@kornel-filep
Copy link
Contributor

kornel-filep commented May 5, 2023

My proposal would be to use 2 (or maybe all 3) from these examples:

  • Fan out a batch job using AWS Step Functions
    This seems like a general use-case where we have to fan out a big batch job. As this comes up a lot during development, including an example with this could be interesting and useful for the audience.
  • Dynamically process data with a Map state
    Data processing and writing to a DynamoDB would increase the scope of this step function testing, but as step functions are used a lot in data pipelines, this might be an interesting scenario to work on as well.
  • Poll for Job Status (Lambda, AWS Batch)
    And this one is just an easy job poller, which when a timeout happens returns with an error. We have a simple condition check in the step function so might as well include it as a simpler example.

@sorosz89 what do you think?

@sorosz89
Copy link

sorosz89 commented May 8, 2023

Good idea, we can even use a simple one as well: Make a call to API Gateway

@szikszail
Copy link
Member Author

https://github.com/Idea-Pool/poc-aws-step-function-cdk-testing

@kornel-filep
Copy link
Contributor

kornel-filep commented May 8, 2023

https://github.com/Idea-Pool/poc-aws-step-function-cdk-testing

We could use this one as well, however in the scope of the topic we would also like to focus on testing step functions as a solution, with reasonable isolation, instead of pure infrastructure testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation section:service
Projects
Development

Successfully merging a pull request may close this issue.

3 participants