fix #1541: Improve deprecation messages

docs/api/options.md

@@ -322,7 +322,7 @@ wrapper.destroy()
 - type: `boolean`
 - default: `false`
 
-::: warning
+::: warning Deprecation warning
 `attachToDocument` is deprecated and will be removed in future releases. Use [`attachTo`](#attachto) instead.
 :::
 

docs/api/wrapper-array/isEmpty.md

@@ -1,6 +1,6 @@
 ## isEmpty
 
-::: warning
+::: warning Deprecation warning
 `isEmpty` is deprecated and will be removed in future releases.
 
 Consider a custom matcher such as those provided in [jest-dom](https://github.com/testing-library/jest-dom#tobeempty).

docs/api/wrapper-array/isVueInstance.md

@@ -1,7 +1,11 @@
 ## isVueInstance
 
-::: warning
+::: warning Deprecation warning
 `isVueInstance` is deprecated and will be removed in future releases.
+
+Most of the times, tests relying on `isVueInstance` provide little to no-value so you could simply remove them.
+
+If you want to keep these tests, a valid replacement is to assert that `wrapper.find(...).vm` exists.
 :::
 
 Assert every `Wrapper` in `WrapperArray` is Vue instance.

docs/api/wrapper-array/setMethods.md

@@ -1,7 +1,13 @@
 ## setMethods
 
-::: warning
+::: warning Deprecation warning
 `setMethods` is deprecated and will be removed in future releases.
+
+There's no clear path to replace `setMethods`, because it really depends on your previous usage. It easily leads to flaky tests that rely on implementation details, which [is discouraged](https://github.com/vuejs/rfcs/blob/668866fa71d70322f6a7689e88554ab27d349f9c/active-rfcs/0000-vtu-api.md#setmethods).
+
+Thus, we suggest to to rethink those tests using the tools Vue Test Utils provides.
+
+If you need to stub out a complex method, extract it out from the component and test it in isolation. On the other hand, if you want to assert that a method is called, use your test runner to spy on it.
 :::
 
 Sets `Wrapper` `vm` methods and forces update on each `Wrapper` in `WrapperArray`.

docs/api/wrapper/emittedByOrder.md

@@ -1,6 +1,6 @@
 ## emittedByOrder
 
-::: warning
+::: warning Deprecation warning
 `emittedByOrder` is deprecated and will be removed in future releases.
 
 Use `wrapper.emitted` instead.

docs/api/wrapper/find.md

@@ -1,6 +1,6 @@
 ## find
 
-::: warning
+::: warning Deprecation warning
 Using `find` to search for a Component is deprecated and will be removed. Use `findComponent` instead.
 :::
 

docs/api/wrapper/findAll.md

@@ -1,6 +1,6 @@
 ## findAll
 
-::: warning
+::: warning Deprecation warning
 Using `findAll` to search for Components is deprecated and will be removed. Use `findAllComponents` instead.
 :::
 

docs/api/wrapper/isEmpty.md

@@ -1,6 +1,6 @@
 ## isEmpty
 
-::: warning
+::: warning Deprecation warning
 `isEmpty` is deprecated and will be removed in future releases.
 
 Consider a custom matcher such as those provided in [jest-dom](https://github.com/testing-library/jest-dom#tobeempty).

docs/api/wrapper/isVisible.md

@@ -1,6 +1,6 @@
 ## isVisible
 
-::: warning
+::: warning Deprecation warning
 `isVisible` is deprecated and will be removed in future releases.
 
 Consider a custom matcher such as those provided in [jest-dom](https://github.com/testing-library/jest-dom#tobevisible).

docs/api/wrapper/isVueInstance.md

@@ -1,7 +1,11 @@
 ## isVueInstance
 
-::: warning
+::: warning Deprecation warning
 `isVueInstance` is deprecated and will be removed in future releases.
+
+Most of the times, tests relying on `isVueInstance` provide little to no-value so you could simply remove them.
+
+If you want to keep these tests, a valid replacement is to assert that `wrapper.find(...).vm` exists.
 :::
 
 Assert `Wrapper` is Vue instance.

docs/api/wrapper/name.md

@@ -1,6 +1,6 @@
 ## name
 
-::: warning
+::: warning Deprecation warning
 `name` is deprecated and will be removed in future releases.
 :::
 

docs/api/wrapper/overview.md

@@ -1,6 +1,6 @@
 ## overview
 
-::: warning
+::: warning Deprecation warning
 `overview` is deprecated and will be removed in future releases.
 :::
 

docs/api/wrapper/setMethods.md

@@ -1,7 +1,13 @@
 ## setMethods
 
-::: warning
+::: warning Deprecation warning
 `setMethods` is deprecated and will be removed in future releases.
+
+There's no clear path to replace `setMethods`, because it really depends on your previous usage. It easily leads to flaky tests that rely on implementation details, which [is discouraged](https://github.com/vuejs/rfcs/blob/668866fa71d70322f6a7689e88554ab27d349f9c/active-rfcs/0000-vtu-api.md#setmethods).
+
+Thus, we suggest to to rethink those tests using the tools Vue Test Utils provides.
+
+If you need to stub out a complex method, extract it out from the component and test it in isolation. On the other hand, if you want to assert that a method is called, use your test runner to spy on it.
 :::
 
 Sets `Wrapper` `vm` methods and forces update.

packages/shared/merge-options.js

@@ -35,7 +35,10 @@ export function mergeOptions(
     [key: string]: Function
   })
   if (methods && Object.keys(methods).length) {
-    warnDeprecated('overwriting methods via the `methods` property')
+    warnDeprecated(
+      'overwriting methods via the `methods` property',
+      'There is no clear migration path for the `methods` property - Vue does not support arbitrarily replacement of methods, nor should VTU. If you need to stub out a method, extract it out and test it. Otherwise, the suggestion is to rethink those tests'
+    )
   }
 
   const provide = (getOption(options.provide, config.provide): Object)

packages/test-utils/src/wrapper.js

@@ -632,7 +632,10 @@ export default class Wrapper implements BaseWrapper {
    * @deprecated
    */
   setMethods(methods: Object): void {
-    warnDeprecated(`setMethods`)
+    warnDeprecated(
+      `setMethods`,
+      `There is no clear migration path for setMethods - Vue does not support arbitrarily replacement of methods, nor should VTU. If you need to stub out a method, extract it out and test it. Otherwise, the suggestion is to rethink those tests`
+    )
 
     if (!this.vm) {
       throwError(`wrapper.setMethods() can only be called on a Vue instance`)

test/specs/config.spec.js

@@ -144,4 +144,58 @@ describeWithShallowAndMount('config', mountingMethod => {
       )
     })
   })
+
+  describe('methods overriding deprecation warning', () => {
+    const expectedErrorMessage = `There is no clear migration path`
+    const Component = {
+      template: '<div></div>',
+      methods: {
+        foo() {}
+      }
+    }
+
+    it('should show warning for options.methods if config is enabled', () => {
+      config.showDeprecationWarnings = true
+
+      mountingMethod(Component, {
+        methods: { foo: () => {} }
+      })
+
+      expect(console.error).to.be.calledWith(
+        sandbox.match(expectedErrorMessage)
+      )
+    })
+
+    it('should not show warning for options.methods if config is disabled', () => {
+      config.showDeprecationWarnings = false
+
+      mountingMethod(Component, {
+        methods: { foo: () => {} }
+      })
+
+      expect(console.error).not.to.be.calledWith(
+        sandbox.match(expectedErrorMessage)
+      )
+    })
+
+    it('should show warning for setMethods if config is enabled', () => {
+      config.showDeprecationWarnings = true
+
+      mountingMethod(Component).setMethods({ foo: () => {} })
+
+      expect(console.error).to.be.calledWith(
+        sandbox.match(expectedErrorMessage)
+      )
+    })
+
+    it('should not show warning for setMethods if config is disabled', () => {
+      config.showDeprecationWarnings = false
+
+      mountingMethod(Component).setMethods({ foo: () => {} })
+
+      expect(console.error).not.to.be.calledWith(
+        sandbox.match(expectedErrorMessage)
+      )
+    })
+  })
 })