chore: migrate from Jest to Vitest (#364)

Author: nickserv

.eslintrc.js

@@ -8,6 +8,7 @@ module.exports = {
     'plugin:react-hooks/recommended',
     'plugin:cypress/recommended',
   ],
+  plugins: ['vitest-globals'],
   parserOptions: {
     ecmaVersion: 2020,
     sourceType: 'module',
@@ -21,7 +22,7 @@ module.exports = {
     browser: true,
     node: true,
     es6: true,
-    jest: true,
+    'vitest-globals/env': true,
   },
   rules: {
     'arrow-body-style': ['error', 'as-needed'],

.github/workflows/ci.yml

@@ -76,7 +76,7 @@ jobs:
           key: ${{ runner.os }}-node_modules-${{ hashFiles('**/package-lock.json') }}
 
       - name: Run Tests
-        run: npm run ci:test
+        run: npm test
   e2e-tests:
     name: e2e Tests
     runs-on: ubuntu-latest

.lintstagedrc.js

@@ -1,7 +1,7 @@
 module.exports = {
   '**/*.js': (files) => [
     `eslint --quiet --fix ${files.join(' ')}`,
-    `jest --passWithNoTests`,
+    `vitest related --run`,
   ],
   '**/*.{md,js,json,yml,html,css}': (files) => [
     `prettier --write ${files.join(' ')}`,

ROADMAP.md

@@ -22,7 +22,7 @@ _Status: Ongoing ([#7](https://github.com/testing-library/testing-playground/iss
 
 A [testing-playground.com] without tests... I don't think that should be a thing, but at this moment it is.
 
-We should fix that, and use jest & testing-library to do it.
+We should fix that, and use Vitest & testing-library to do it.
 
 ## Usage instructions