[Feature Request] Avoid importing globally Vuetify in all tests

Versions and Environment

Vuetify: ^1.1.11 Vue: 2.5.16 Browsers: all OS: all

Previously worked in:

Vuetify: ^1.1.10 Vue: 2.5.16

Steps to reproduce

Since Vuetify version 1.1.11, developers have to import globally Vuetify in all tests to avoid having 2 multiples Vue instances running (and see a warning referring to #4068 )

localVue.use(Vuetify)

has been replaced by

Vue.use(Vuetify)

Expected Behavior

Using localVue is better because it prevents polluting the original Vue copy during tests. I expect Vuetify not to use its own instance of Vue. So I can come back using only localVue.use(Vuetify) in all of my tests

Actual Behavior

I had to use Vue.use(Vuetify) in each of my test files

Reproduction Link

https://codesandbox.io/s/mz86zx5vnj

Watch the warnings generated by the test

Additional Comments:

[stas-kh]

This is super confusing, guys. Any updates here?

[johnleider]

An update on this issue. Currently with how we must extend the Vue object in order to have proper typescript support, you will have to bootstrap Vue in your test setup file:

// tests/setup.js

import Vue from 'vue'
import Vuetify from 'vuetify'

Vue.use(Vuetify)

I have dropped the ball on providing clear documentation on how to do this and for that I apologize. This is something that I will be adding to the documentation in the coming weeks for the next version.

In regards to a long term solution, I’m accepting any and all suggestions on how to accommodate typescript support while also enabling the bootstrapping of localVue.