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
dreamorosi opened this issue
Oct 23, 2024
· 2 comments
· Fixed by #3299
Assignees
Labels
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parserThis item relates to the Parser UtilitytestsPRs that add or change tests
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.
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.
The text was updated successfully, but these errors were encountered:
dreamorosi
added
confirmed
The scope is clear, ready for implementation
internal
PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
parser
This item relates to the Parser Utility
tests
PRs that add or change tests
labels
Oct 23, 2024
completedThis item is complete and has been merged/shippedinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)parserThis item relates to the Parser UtilitytestsPRs that add or change tests
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
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: