FAQ
See also the main FAQ for questions not specific to Vue testing.
Is Vue Testing Library a replacement for the official @vue/test-utils?
Short answer: yes, it is. If you use Vue Testing Library (VTL) there's no need to install @vue/test-utils.
Longer answer: VTL is built on top of @vue/test-utils. The official library is
used to render Vue components (by calling mount
) and exposes some of
its methods (while hiding others). You can check the full list of available
methods in the API section.
Do I need to install DOM Testing Library?
Nope! VTL imports everything it needs from DOM Testing Library, and then re-exports it.
What queries does Vue Testing Library provide?
All queries from DOM Testing Library. See Queries for full list.
If I can't use shallow rendering, how do I mock out components in tests?
In general, you should avoid mocking out components (see the Guiding Principles section).
However if you need to, you can either use Jest's
mocking feature or
the stubs
key provided by @vue/test-utils.
import { render } from '@vue/test-utils'
import Component from './Component'
test('Can stub components', () => {
render(Component, {
stubs: ['FontAwesomeIcon'],
})
})
You can check out a working example in the GitHub repository of VTL.
How can I test if an element has appeared / has disappeared?
Check the Appearance and Disappearance section of the Guide for available methods to test appearance and disappearance.
If you want to check if an element was never rendered, you might want to write something like the following:
expect(queryByText('submit')).toBeNull()
// or, if using extend/expect:
import '@testing-library/jest-dom/extend-expect'
expect(queryByText('submit')).not.toBeInTheDocument()