test: convert some packages unit and e2e tests to vitest #6584
Conversation
kuhe
changed the title
| @@ -34,8 +35,7 @@ class AnyCommand extends DynamoDBDocumentClientCommand<{}, {}, {}, {}, {}> { | |||
| } | |||
|
|
|||
| describe("DynamoDBDocumentClientCommand", () => { | |||
| // ToDo: Investigate why Jest29 throws TypeError: Class constructor Command cannot be invoked without 'new' | |||
| it.skip("should not allow usage of the default middlewareStack", () => { | |||
| it("should not allow usage of the default middlewareStack", () => { | |||
There was a problem hiding this comment.
one benefit shown here, it works around certain Jest problems
| ], | ||
| environment: "node", | ||
| }, | ||
| }); |
There was a problem hiding this comment.
This config file explicitly lists out packages because not all .spec.ts files are vitest compatible.
In CI, test:unit is run by turbo, so this file is not used, and does not need to be maintained. When conversion is complete, the inclusion will be wild-card based instead of curated, and only used if a developer wishes to run npx vite run etc. from the root.
| include: ["lib/lib-dynamodb/**/*.e2e.spec.{ts,js}", "lib/lib-storage/**/*.e2e.spec.{ts,js}"], | ||
| environment: "node", | ||
| }, | ||
| }); |
There was a problem hiding this comment.
This is not part of CI. It is a temporary local-dev file for running vitest e2e tests from the application root.
|
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. |
libunit and e2e to vitest.packageunit and e2e to vitest for packages starting with letters A-E.Testing
running the tests