-
-
Notifications
You must be signed in to change notification settings - Fork 19
update test suites #1668
Copy link
Copy link
Open
Labels
DevOpstype of development task related to Process, Github Actions, and Deploymenttype of development task related to Process, Github Actions, and DeploymentdependencyThe issue or reason why this issue is in the iceboxThe issue or reason why this issue is in the iceboxfeature: technical standardsaccessibility, usability, unit testing, etc.accessibility, usability, unit testing, etc.issue level: missingissue type I: requestSmallest type of issue; Typically can be completed by one personSmallest type of issue; Typically can be completed by one personpriority: mediumrole: developmentanything related to codeanything related to codesize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Milestone
Description
Metadata
Metadata
Assignees
Labels
DevOpstype of development task related to Process, Github Actions, and Deploymenttype of development task related to Process, Github Actions, and DeploymentdependencyThe issue or reason why this issue is in the iceboxThe issue or reason why this issue is in the iceboxfeature: technical standardsaccessibility, usability, unit testing, etc.accessibility, usability, unit testing, etc.issue level: missingissue type I: requestSmallest type of issue; Typically can be completed by one personSmallest type of issue; Typically can be completed by one personpriority: mediumrole: developmentanything related to codeanything related to codesize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Type
Fields
No fields configured for issues without a type.
Projects
StatusShow more project fields
Icebox
Dependency
Overview
Create React App(CRA) deprecated and we had to migrate to Vite for future sustainability. However many of our test suites from #1241 use testing packages from CRA. We need to translate these test suites to use Vite-compatible tests.
Action Items
Update the test suites using the new test library:
Root folder
vitestand@vitest/typesnpm packagesjestnpm run testusesvitestcommand instead ofreact-scripts testdefineConfigin addition to plugins@testing-library/jest-domimportbeforeEach, used in input button/routing tests) sequentially in Vitest, you can configure Vitest's sequence.hooks to 'list' in the test object"types": ["vitest"],undercompilerOptionsIndividual test files
import { describe, test, expect, vi } from 'vitest';vi.fn()instead ofjest.fn()to mock functionsThere may be additional updates needed based on the specifics of each test file, but this should get us most of the way there.
new issue approvalcolumnnew issue approvalcolumnResources/Notes
Vitest - Jest migration docs