generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 175
Closed
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change testsPRs that add or change tests
Description
Summary
The packages/event-handler/tests/unit/rest/BaseRouter.test.ts
file is nearly 1900 lines in size and will only get bigger as we add more functionality to this event handler. We should break this monolith up in multiple files that test different areas of functionality. We can use the describe blocks as a guide on how to split the tests up.
Why is this needed?
The cognitive load of such a large file slows development and makes the suite harder to extend.
Which area does this relate to?
Tests
Solution
We should break this monolith up in multiple files that test different areas of functionailty. We can use the describe blocks as a guide on how to split the tests up.
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
completedThis item is complete and has been merged/shippedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change testsPRs that add or change tests
Type
Projects
Status
Shipped