Jamie Tanna 066c7026e7 test: correctly call toMigrate with vitest (#38242) ...

fix(tests): correctly call `async toMigrate` with vitest

While working on #38240, I noticed that the failing tests I was
writing didn't trigger.

It turns out that in 997c23502e, when we
migrated to Vitest, and made some functions `async`, we missed out on
making the tests themselves `async`.

This correctly applies the `async` modifier to test functions, allowing
them to correctly pass/fail when running async code.

We can also make sure that `toMigrate` is returning a Promise to
indicate it's asynchronous.

2025-09-27 08:29:30 +00:00

..

docs

test: use async (#36953)

2025-07-12 12:35:51 +00:00

e2e

chore: remove rarkins from maintainers (#37585)

2025-08-29 08:36:42 +00:00

other

refactor(zod): rename schema to match our best practices guide (#37499)

2025-08-14 10:35:03 +00:00

types

test: migrate more to vitest (#34500)

2025-02-26 15:45:17 +00:00

exec-util.ts

test: cleanup (#34785)

2025-03-13 17:52:09 +00:00

fixtures.ts

test: migrate to vitest (#34475)

2025-02-26 09:35:54 +00:00

graphql-snapshot.ts

chore(deps): update eslint monorepo to v9 (major) (#33573)

2025-02-20 11:31:13 +00:00

host-rules.ts

test: fix code coverage (#34495)

2025-02-26 12:40:30 +00:00

http-mock.ts

feat: refactor http (#34550)

2025-02-28 14:40:04 +00:00

s3.ts

test: migrate to vitest (#34475)

2025-02-26 09:35:54 +00:00

setup.ts

test: cleanup (#34785)

2025-03-13 17:52:09 +00:00

to-migrate.ts

test: correctly call toMigrate with vitest (#38242)

2025-09-27 08:29:30 +00:00

util.ts

feat(config): managerFilePatterns (#34615)

2025-05-04 08:30:24 +00:00