From c439053d4836d6bcd3e802da4d8ac12233edddd4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81tila=20Camur=C3=A7a=20Alves?= <camurca.home@gmail.com>
Date: Wed, 7 Aug 2019 09:49:56 -0300
Subject: [PATCH] Update common-tips.md

Explicitly importing `mount`, for a more complete example.
---
 docs/guides/common-tips.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guides/common-tips.md b/docs/guides/common-tips.md
index d3d1a0d32..229683e25 100644
--- a/docs/guides/common-tips.md
+++ b/docs/guides/common-tips.md
@@ -143,7 +143,7 @@ Some of the components may rely on features injected by a global plugin or mixin
 If you are writing tests for components in a specific app, you can setup the same global plugins and mixins once in the entry of your tests. But in some cases, for example testing a generic component suite that may get shared across different apps, it's better to test your components in a more isolated setup, without polluting the global `Vue` constructor. We can use the [`createLocalVue`](../api/createLocalVue.md) method to achieve that:
 
 ```js
-import { createLocalVue } from '@vue/test-utils'
+import { createLocalVue, mount } from '@vue/test-utils'
 
 // create an extended `Vue` constructor
 const localVue = createLocalVue()