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
Nov 25, 2024
· 0 comments
· Fixed by #3355
Assignees
Labels
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change 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.)
tests
PRs that add or change tests
labels
Nov 25, 2024
confirmedThe scope is clear, ready for implementationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)testsPRs that add or change tests
Summary
To continue the migration from Jest to Vitest we need to move over the tests for the metrics package to use the new test runner.
Why is this needed?
So that we can continue the migration as well as improve the overall performance and consistency of the tests.
Which area does this relate to?
Tests
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: