-
Notifications
You must be signed in to change notification settings - Fork 161
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.)parserThis item relates to the Parser UtilityThis item relates to the Parser UtilitytestsPRs that add or change testsPRs that add or change tests
Description
Summary
To continue the migration from Jest to Vitest we need to move over the tests for the parser
package to use the new test runner.
In doing so, we can also take the opportunity to streamline the test setup by avoiding loading all events for each test file/case, and remove unused/redundant test cases/events.
Why is this needed?
So that we can continue the migration as well as improve the overall performance and correctness of the tests, which currently rely on heavy I/O and might contain flawed assumptions/tests.
Which area does this relate to?
Parser
Solution
No response
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.)parserThis item relates to the Parser UtilityThis item relates to the Parser UtilitytestsPRs that add or change testsPRs that add or change tests
Type
Projects
Status
Shipped