chore: migrate core (autocomplete) tests to vitest #6063
Conversation
- also include .test.ts files for vitest config
|
Your cubic subscription is currently inactive. Please reactivate your subscription to receive AI reviews and use cubic. |
✅ Deploy Preview for continuedev canceled.
|
dosubot
bot
added
the
size:L
| @@ -46,7 +46,7 @@ export async function testRootPathContext( | |||
|
|
|||
| // Copy the folder to the test directory | |||
| const folderPath = path.join( | |||
| __dirname, | |||
There was a problem hiding this comment.
vitest gets the actual __dirname where the file resides while for jest __dirname is equivalent process.cwd()
for example, in this case, __dirname for vitest would be /users/myuser/continue/core/autocomplete/context/root-path-context/test and for jest it would be /users/myuser/continue/core
Hence used process.cwd()
uinstinct
changed the title
|
|
![recurseml[bot]](https://avatars.githubusercontent.com/in/1054195?s=60&v=4){kind=small}
| @@ -1,3 +1,4 @@ | |||
| import { describe, test } from "vitest"; | |||
There was a problem hiding this comment.
Missing required 'expect' import for test assertions. While 'describe' and 'test' are imported, the test file uses assertions that require the 'expect' function from Vitest. Without importing 'expect', the test assertions will fail at runtime. The import should be modified to include 'expect': import { describe, test, expect } from "vitest";
React with 👍 to tell me that this comment was useful, or 👎 if not (and I'll stop posting more comments like this in the future)
|
😱 Found 1 issue. Time to roll up your sleeves! 😱 |
core/vitest.config.ts
Outdated
| "config/yaml/LocalPlatformClient.test.ts", | ||
| "autocomplete/**/*.test.ts", |
There was a problem hiding this comment.
As we spoke on the huddle earlier today, let's only include ["**/*.vitest.ts"] and update test names accordingly instead.
Description
As part of our migration of tests inside
corefrom jest to vitest, this PR:autocompletedirectory.related to CON-2030
Checklist
Screenshots
[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]
Tests
[ What tests were added or updated to ensure the changes work as expected? ]