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
While writing unit tests and end-to-end tests for Serverless applications is similar to traditional applications, other types of tests (such as integration tests, acceptance tests, component tests) are more challenging.
We want to explore ways this can be made easier, and need your feedback. Here are a few ideas we are thinking about -
Manage timeouts and retries for tests targeting event driven applications
Optimize test execution time
Auto generate test payloads for a set of AWS services
Invoke using auto generated payloads
Asserting on event payloads
Injecting failures
Set up a test environment to run tests in an isolated manner
Please feel free to drop your ideas/requests pertaining to integration testing in the comments. Specifically, what are the sticky issues you run into when writing tests for Serverless applications on AWS? Do the ideas above accurately address the pain points?
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
While writing unit tests and end-to-end tests for Serverless applications is similar to traditional applications, other types of tests (such as integration tests, acceptance tests, component tests) are more challenging.
We want to explore ways this can be made easier, and need your feedback. Here are a few ideas we are thinking about -
Please feel free to drop your ideas/requests pertaining to integration testing in the comments. Specifically, what are the sticky issues you run into when writing tests for Serverless applications on AWS? Do the ideas above accurately address the pain points?
The text was updated successfully, but these errors were encountered: