chore: Convert ATs to Vitest #1181
Conversation
| testTimeout: 30000, | ||
| hookTimeout: 20000, |
There was a problem hiding this comment.
I doubt the tests should take this long, I just went a little high to prevent false positives
| opts.env = { BROWSER: 'none' }; | ||
| } | ||
| // Prevent the browser from opening when `open` is called | ||
| opts.env = { BROWSER: 'none' }; |
There was a problem hiding this comment.
I removed the check for the headless config value, because I can't think of why we would want to open browser windows. We don't plan on interacting with them from the tests and all it does is make your system borderline unusable for the duration of the tests.
| @@ -66,7 +51,7 @@ const getTestConfig = () => { | |||
| } | |||
|
|
|||
| if (!config.cliPath && !config.cliVersion) { | |||
| const defaultPath = path.join(process.cwd(), DEFAULT_CLI_PATH); | |||
There was a problem hiding this comment.
DEFAULT_CLI_PATH was only used in one place and it's relative to the cwd, so it seem to make more sense to just inline it.
| "js-yaml": "^4.0.0", | ||
| "rimraf": "^3.0.2", | ||
| "uuid": "^10.0.0", |
There was a problem hiding this comment.
Add the uuid lib to help with file name randomization
| import rimraf from 'rimraf'; | ||
| import { v4 as uuidv4 } from 'uuid'; | ||
|
|
||
| export class TestState { |
There was a problem hiding this comment.
This is a helper class to manage all of the state needed to be able to run the tests. It helps to segment the tests so they all have their own copy of the test state and can run in isolation from one another. It handles the generation of a config file with a semi-randomized name so file system collisions should not happen between tests.
|
|
||
| # Acceptance Tests | ||
| acceptance-tests/my-project | ||
| acceptance-tests/*.yml |
…ion of another test
There was a problem hiding this comment.
Nice! This seems like such a huge upgrade. Everything here looks good to me aside from a few tiny things.
I'm having trouble getting these to run locally. Is there anything special you need to do? Ran yarn and yarn test but getting errors
Error: Invalid process path hs
Description and Context
vitestopenis calledTODO
Who to Notify
@kemmerle @camden11 @brandenrodgers