title: [vue-test-utils]: overwriting methods via the `methods` property or setMethods is deprecated
body: <p>I am trying to test the <code>methods</code> of my Vue components; the test is seems working fine. But the problem is that it's giving a depreciation warning in the console.</p>
  <p>I believe that the <code>vue-test-utils</code> teams would be removing the <code>setMethods</code> and <code>methods</code> property in their next major release.</p>
  <p>My problem is that there are no alternative ways to achieve the same things provided for both <code>setMethods</code> and <code>methods property</code>.</p>
  <p>Just they suggested a warning:</p>
  <pre><code>To stub a complex method extract it from the component and test it in isolation. Otherwise, the suggestion is to rethink those tests.
  </code></pre>
  <p><strong>My Question: How can we extract the method and test the functionalities of the method clicked from the component level or not?</strong></p>
  <p>Below is my simple example where I mocked a method and checking if it gets called inside the component when triggered click.</p>
  <pre><code>const downloadStub = jest.fn()
  const wrapper = mount(Documents, {
    methods: { downloadNow: downloadStub },
  })
  it('check download button clicked and calling downloadNow method', () =&gt; {
    wrapper.find('.download-button').trigger('click')
    expect(downloadStub).toBeCalled()
  })
  </code></pre>
  <p><strong>Note:</strong> No issues in running the above code; I want to know the alternative ways to achieve the same result and avoid the warning?</p>