test(maintenance): switch tracer to vitest #3285
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
automation
pull-request-size
bot
added
the
size/XXL
|
Integration tests passing on this branch: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/11669742574/job/32492395223 |
am29d
requested changes
Nov 5, 2024
|
@am29d thanks for the review, addressed your comments & ready for another round. |
|
am29d
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
This PR moves the unit and end to end tests for the Tracer package to use vitest as test runner.
This action is part of the ongoing migration from Jest to Vitest, and the vast majority of the changes in the tests focus on changing the imports and using Vitest-specific APIs.
The file with most changes is the
packages/tracer/tests/unit/Provider.test.ts, which has a module import mock for theaws-xray-sdk-nodepackage. Because Jest and Vitest mock imports slightly differently, I had to make more changes in this file than in others.I also have removed some redundant test cases while maintaining the same level of coverage.
Two extra files from other packages were touched, respectively for:
setupEnv.tsunderpackages/testingwas modified to include two environment variables needed for Tracer during tests.Issue number: closes #3284
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.