The key to writing unit tests for Vue components is to choose the right tools and master the basic routines. 1. Vitest is suitable for modern projects and is fast; Jest is mature in ecosystem and has good compatibility. 2. To install and configure Vitest, you need to add plug-ins and set up scripts; Jest needs to create configuration files and install related dependencies. 3. When writing test cases, use mount to simulate real behavior, and note that await should be used for asynchronous operations. 4. During testing, mock external dependencies, deal with asynchronous rendering, avoid overtesting styles, and splitting complex logic. 5. Persisting in running the test after each modification can effectively reduce bugs.
It is actually not difficult to write unit tests for Vue components. The key is to choose the right tools and master the basic routines. Vitest and Jest are both mainstream choices. If used properly, they can help you discover many potential problems and improve the quality of your code.

Install and configure Vitest or Jest
First determine which test framework you want to use. Vitest is based on Vite, fast and suitable for modern projects; Jest is more mature, has a richer ecosystem and better compatibility.

Vitest:
-
Installation dependencies:
npm install -D vitest @vitejs/plugin-vue vue-test-utils
Add plugin in
vite.config.js
:import { defineConfig } from 'vite' import vue from '@vitejs/plugin-vue' export default defineConfig({ plugins: [vue()] })
Add script to
package.json
:"scripts": { "test:unit": "vitest" }
Jest:
Installation dependencies:
npm install -D jest @vue/test-utils@next vue-jest babel-jest
Create
jest.config.js
file:module.exports = { testEnvironment: 'jsdom', transform: { '^. \\.vue$': 'vue-jest', '^. \\.js$': 'babel-jest' }, moduleNameMapper: { '^@/(.*)$': '<rootDir>/src/$1' } }
Add script:
"scripts": { "test:unit": "jest" }
Write the first component test
Take a simple button component as an example: the number increases after clicking.
<!-- CounterButton.vue --> <template> <button @click="count ">Clicked {{ count }} times</button> </template> <script setup> import { ref } from 'vue' const count = ref(0) </script>
Corresponding test files:
// CounterButton.test.js import { mount } from '@vue/test-utils' import CounterButton from './CounterButton.vue' test('increments count when clicked', async () => { const wrapper = mount(CounterButton) await wrapper.trigger('click') expect(wrapper.text()).toContain('Clicked 1 times') })
A few notes:
- Using
mount
instead ofshallowMount
can simulate behavior more realistically. -
await
should be used for asynchronous operations, such as event triggering, data update, etc. - Don't just measure the rendering results, but also cover the interactive logic.
Testing tips and precautions
Mock to remove external dependencies : If your component calls the API or uses Vuex/Pinia, remember to mock to remove these parts and make sure that the test focuses on the component itself.
Example (mock axios):
jest.mock('axios', () => ({ get: jest.fn(() => Promise.resolve({ data: 'mocked data' })) }))
Handling asynchronous rendering : Vue updates the DOM asynchronously, so you need to use
await nextTick()
orawait flushPromises()
to wait for the update to complete.Avoid overtesting styles : Don't test font colors or margins such as easy to change, focus on testing structure and logic.
Split complex logic into testable functions : If there is a lot of business logic in the component, it is recommended to extract it into a separate function, which makes it easier to do unit testing.
Basically that's it. Unit tests for writing Vue components are not complicated, but it is easy to ignore details. As long as you insist on running the test every time you make a correction, you can greatly reduce the probability of bugs.
The above is the detailed content of Unit Testing Vue Components with Vitest/Jest. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

React itself does not directly manage focus or accessibility, but provides tools to effectively deal with these issues. 1. Use Refs to programmatically manage focus, such as setting element focus through useRef; 2. Use ARIA attributes to improve accessibility, such as defining the structure and state of tab components; 3. Pay attention to keyboard navigation to ensure that the focus logic in components such as modal boxes is clear; 4. Try to use native HTML elements to reduce the workload and error risk of custom implementation; 5. React assists accessibility by controlling the DOM and adding ARIA attributes, but the correct use still depends on developers.

Shallowrenderingtestsacomponentinisolation,withoutchildren,whilefullrenderingincludesallchildcomponents.Shallowrenderingisgoodfortestingacomponent’sownlogicandmarkup,offeringfasterexecutionandisolationfromchildbehavior,butlacksfulllifecycleandDOMinte

StrictMode does not render any visual content in React, but it is very useful during development. Its main function is to help developers identify potential problems, especially those that may cause bugs or unexpected behavior in complex applications. Specifically, it flags unsafe lifecycle methods, recognizes side effects in render functions, and warns about the use of old string refAPI. In addition, it can expose these side effects by intentionally repeating calls to certain functions, thereby prompting developers to move related operations to appropriate locations, such as the useEffect hook. At the same time, it encourages the use of newer ref methods such as useRef or callback ref instead of string ref. To use Stri effectively

Create TypeScript-enabled projects using VueCLI or Vite, which can be quickly initialized through interactive selection features or using templates. Use tags in components to implement type inference with defineComponent, and it is recommended to explicitly declare props and emits types, and use interface or type to define complex structures. It is recommended to explicitly label types when using ref and reactive in setup functions to improve code maintainability and collaboration efficiency.

Server-siderendering(SSR)inNext.jsgeneratesHTMLontheserverforeachrequest,improvingperformanceandSEO.1.SSRisidealfordynamiccontentthatchangesfrequently,suchasuserdashboards.2.ItusesgetServerSidePropstofetchdataperrequestandpassittothecomponent.3.UseSS

WebAssembly(WASM)isagame-changerforfront-enddevelopersseekinghigh-performancewebapplications.1.WASMisabinaryinstructionformatthatrunsatnear-nativespeed,enablinglanguageslikeRust,C ,andGotoexecuteinthebrowser.2.ItcomplementsJavaScriptratherthanreplac

Vite or VueCLI depends on project requirements and development priorities. 1. Startup speed: Vite uses the browser's native ES module loading mechanism, which is extremely fast and cold-start, usually completed within 300ms, while VueCLI uses Webpack to rely on packaging and is slow to start; 2. Configuration complexity: Vite starts with zero configuration, has a rich plug-in ecosystem, which is suitable for modern front-end technology stacks, VueCLI provides comprehensive configuration options, suitable for enterprise-level customization but has high learning costs; 3. Applicable project types: Vite is suitable for small projects, rapid prototype development and projects using Vue3, VueCLI is more suitable for medium and large enterprise projects or projects that need to be compatible with Vue2; 4. Plug-in ecosystem: VueCLI is perfect but has slow updates,

Immutable updates are crucial in React because it ensures that state changes can be detected correctly, triggering component re-rendering and avoiding side effects. Directly modifying state, such as push or assignment, will cause React to be unable to detect changes. The correct way to do this is to create new objects instead of old objects, such as updating an array or object using the expand operator. For nested structures, you need to copy layer by layer and modify only the target part, such as using multiple expansion operators to deal with deep attributes. Common operations include updating array elements with maps, deleting elements with filters, adding elements with slices or expansion. Tool libraries such as Immer can simplify the process, allowing "seemingly" to modify the original state but generate new copies, but increase project complexity. Key tips include each
