Skip to content

test(endpoints): migrate from jest to vitest#7908

Merged
trivikr merged 2 commits intomainfrom
trivikr/test-endpoints-vitest
Apr 1, 2026
Merged

test(endpoints): migrate from jest to vitest#7908
trivikr merged 2 commits intomainfrom
trivikr/test-endpoints-vitest

Conversation

@trivikr
Copy link
Copy Markdown
Member

@trivikr trivikr commented Mar 31, 2026

Issue

Noticed in #7906

Description

Migrates endpoint tests from jest to vitest

Testing

Before

Tests are run using jest

$ aws-sdk-js-v3> make test-endpoints
npx jest -c ./tests/endpoints-2.0/jest.config.js --bail --verbose false
 PASS  tests/endpoints-2.0/endpoints-integration.spec.ts (22.277 s)

Test Suites: 1 passed, 1 total
Tests:       5 skipped, 13901 passed, 13906 total
Snapshots:   0 total
Time:        22.367 s
Ran all test suites.

After

Tests are run using vitest

$ aws-sdk-js-v3> make test-endpoints
...
 Test Files  1 passed (1)
      Tests  13901 passed | 5 skipped (13906)
   Start at  18:21:06
   Duration  7.81s (transform 50ms, setup 0ms, import 5.52s, tests 1.94s, environment 0ms)

Checklist

  • If the PR is a feature, add integration tests (*.integ.spec.ts) or E2E tests.
    • It's not a feature.
  • My E2E tests are resilient to concurrent i/o.
    • I didn't write any E2E tests.
  • I added access level annotations e.g. @public, @internal tags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.
    • I didn't add any public functions.
  • Streams - how do they work?? My WebStream readers/locks are properly lifecycled. Node.js stream backpressure is handled. Error handling.
    • No streams here.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@trivikr trivikr requested a review from a team as a code owner March 31, 2026 18:29
@trivikr trivikr merged commit 7ed15be into main Apr 1, 2026
7 checks passed
@trivikr trivikr deleted the trivikr/test-endpoints-vitest branch April 1, 2026 17:38
@github-actions
Copy link
Copy Markdown

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants