feat(backend): vitest #4296
feat(backend): vitest #4296
Conversation
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
jacekradko
force-pushed
the
jacek/backend-vitest
branch
from
d33a518
to
c70d74d
Compare
| @@ -88,7 +88,7 @@ export function buildRequest(options: BuildRequestOptions) { | |||
| let res: Response | undefined; | |||
| try { | |||
| if (formData) { | |||
| res = await runtime.fetch(finalUrl.href, { | |||
| res = await (process.env.NODE_ENV === 'test' ? fetch : runtime.fetch)(finalUrl.href, { | |||
There was a problem hiding this comment.
Will need to think about a more ergonomic way of accomplishing this. With the way fetch is handled in the package, msw can't intercept requests without it for now
| }); | ||
| expect(jwk).toMatchObject(mockRsaJwk); | ||
| jwk = await loadClerkJWKFromRemote({ | ||
| secretKey: 'deadbeef', |
Check failure
Code scanning / CodeQL
Hard-coded credentials Critical test
| // cache should be cleared, but 5m ttl is still valid | ||
| fakeClock.next(); | ||
| jwk = await loadClerkJWKFromRemote({ | ||
| secretKey: 'deadbeef', |
Check failure
Code scanning / CodeQL
Hard-coded credentials Critical test
Description
Spiking out
vitesttest runner as a replacement forqunitin@clerk/backendRelated: https://linear.app/clerk/issue/SDKI-694/refactor-clerkbackend-to-use-vitest-instead-of-qunit
Checklist
npm testruns as expected.npm run buildruns as expected.Type of change