Testing Library

Testing Library

  • Docs
  • Recipes
  • Help
  • Blog

›Vue Testing Library

Getting Started

  • Introduction
  • Guiding Principles
  • Using Fake Timers

Frameworks

    DOM Testing Library

    • Introduction
    • Install
    • Example
    • Setup
    • Queries
    • Firing Events
    • Async Utilities
    • Helpers
    • Configuration
    • FAQ
    • Cheatsheet

    React Testing Library

    • Introduction
    • Example
    • Setup
    • API
    • Migrate from Enzyme
    • FAQ
    • Cheatsheet

    Reason Testing Library

    • Introduction
    • Examples

    React Native Testing Library

    • Introduction
    • Example
    • Setup

    Vue Testing Library

    • Introduction
    • Examples
    • Setup
    • API
    • Cheatsheet
    • FAQ

    Marko Testing Library

    • Introduction
    • Setup
    • API

    Angular Testing Library

    • Introduction
    • Examples
    • API

    Preact Testing Library

    • Introduction
    • Example
    • API
    • Learn

    Svelte Testing Library

    • Introduction
    • Setup
    • Example
    • API
  • Cypress Testing Library
  • Puppeteer Testing Library
  • Testcafe Testing Library
  • Nightwatch Testing Library

Ecosystem

  • user-event
  • jest-dom
  • bs-jest-dom
  • jest-native
  • react-select-event
  • eslint-plugin-testing-library
  • eslint-plugin-jest-dom
  • riot-testing-library
  • jasmine-dom
Edit

API

Vue Testing Library re-exports everything from DOM Testing Library.

It also exposes these methods:

  • render(Component, options, callback)
    • Parameters
      • Component
      • Options
      • Callback Function
    • render result
      • ...queries
      • container
      • baseElement
      • debug(element)
      • unmount()
      • isUnmounted()
      • html()
      • emitted()
      • updateProps(props)
  • fireEvent
    • touch(elem)
    • update(elem, value)
  • cleanup

render(Component, options, callback)

The render function is the only way of rendering components in Vue Testing Library.

It takes up to 3 parameters and returns an object with some helper methods.

function render(Component, options, callbackFunction) {
  return {
    ...DOMTestingLibraryQueries,
    container,
    baseElement,
    debug,
    unmount,
    isUnmounted,
    html,
    emitted,
    updateProps,
  }
}

Parameters

Component

The valid Vue Component to be tested.

Options

An object containing additional information to be passed to @vue/test-utils mount.

Additionally, the options object can also include the following three keys:

  1. store - The object definition of a Vuex store.
  2. routes - A set of routes for Vue Router.
  3. props - It will be merged with propsData.

If a store object is provided, Vue Testing Library will import and configure a Vuex store.

Similarly, if routes is provided, the library will import and configure Vue Router.

Callback Function

function callbackFunction(vueInstance, vuexStore, router) {}

A callback function that receives the Vue instance as a parameter. This allows 3rd party plugins to be installed prior to mount.

The function will also receive the Store or the Router object if the associated option was passed in during render.

render result

The render method returns an object that has a few properties:

...queries

The most important feature of render is that the queries from DOM Testing Library are automatically returned with their first argument bound to the baseElement, which defaults to document.body.

See Queries for a complete list of available methods.

const { getByLabelText, queryAllByTestId } = render(Component)

container

By default, Vue Testing Library will create a div and append it to the baseElement. This is where your component will be rendered. If you provide your own HTMLElement container via this option, it will not be appended to the baseElement automatically.

const table = document.createElement('table')

const { container } = render(TableBody, {
  container: document.body.appendChild(table),
})

Tip: To get the root element of your rendered element, use container.firstChild.

baseElement

baseElement is used as the base element for the queries as well as what is printed when you use debug().

It matches container if no custom baseElement is provided. If neither baseElement or container options are provided, baseElement defaults to document.body.

debug(element)

This method is a shortcut for console.log(prettyDOM(element)).

element can either be a DOM element or an array containing DOM elements. It defaults to baseElement

import { render } from '@testing-library/vue'

const HelloWorldComponent {
  template: `<h1>Hello World</h1>`
}

const { debug } = render(HelloWorldComponent)
debug()
// <div>
//   <h1>Hello World</h1>
// </div>

// you can also pass an element: debug(getByTestId('messages'))

This is a simple wrapper around prettyDOM which is also exposed and comes from DOM Testing Library.

unmount()

An alias for @vue/test-utils destroy.

isUnmounted()

Returns whether if a Vue component has been destroyed.

html()

An alias for @vue/test-utils html.

emitted()

An alias for @vue/test-utils emitted.

updateProps(props)

An alias for @vue/test-utils setProps.

It returns a Promise through wait(), so you can await updateProps(...).


fireEvent

Vue Testing Library re-exports all DOM Testing Library firing events. However, it alters them so that all events are async.

await fireEvent.click(getByText('Click me'))

Additionally, Vue Testing Library exposes two useful methods:

touch(elem)

It triggers both focus() and blur() events.

await fireEvent.touch(getByLabelText('username'))

// Same as:
await fireEvent.focus(getByLabelText('username'))
await fireEvent.blur(getByLabelText('username'))

update(elem, value)

Properly handles inputs controlled by v-model. It updates the input/select/textarea inner value while emitting the appropriate native event.

See a working example of update in the v-model example test.


cleanup

Unmounts Vue trees that were mounted with render.

If you are using an environment that supports afterEach hook (as in Jest), there's no need to call cleanup manually. Vue Testing Library handles it for you.

Failing to call cleanup when you've called render could result in a memory leak and tests which are not idempotent (which can lead to difficult to debug errors in your tests).

Last updated on 5/25/2020
← SetupCheatsheet →
  • render(Component, options, callback)
    • Parameters
    • render result
  • fireEvent
    • touch(elem)
    • update(elem, value)
  • cleanup
Testing Library
Docs
Getting StartedExamplesAPIHelp
Community
BlogStack OverflowDiscord
More
StarGitHubEdit Docs on GitHubHosted by Netlify
Copyright © 2018-2020 Kent C. Dodds and contributors