Skip to content

Releases: testing-library/vue-testing-library

v5.0.3

20 May 16:32
7a7c0fd
Compare
Choose a tag to compare

5.0.3 (2020-05-20)

@vue/[email protected] now stubs transitions by default. After updating, some tests might fail because of this. The easiest solution is to disable stubbing for transitions for those tests:

test('should mount', () => {
  const { ... } = render(ComponentWithTransitions, {
    stubs: {
      transition: false;
    }
  })
})

v5.0.2

18 Mar 11:10
d628f36
Compare
Choose a tag to compare

5.0.2 (2020-03-18)

Bug Fixes

v5.0.1

17 Mar 14:18
58a4b5a
Compare
Choose a tag to compare

5.0.1 (2020-03-17)

Bug Fixes

  • mocha: allow vue-router creation using mocha (#127) (58a4b5a), closes #119

v5.0.0

13 Mar 08:55
c79a388
Compare
Choose a tag to compare

5.0.0 (2020-03-13)

Features

  • Update @testing-library/dom (#125) (c79a388)
  • Update minor/patch versions for other libraries, such as @vue/test-utils.

BREAKING CHANGES

  • The latest version of DOM Testing Library has several breaking changes, so you will want to review its changelog to ensure you are unaffected.

  • This release drops support for Node 8. Upgrade to Node 10 or greater.

v4.2.0

04 Mar 10:28
850bd4c
Compare
Choose a tag to compare

4.2.0 (2020-03-04)

Features

  • screen: add screen export from DTL + Update deps (#121) (850bd4c)

v4.1.0

21 Oct 10:18
Compare
Choose a tag to compare

4.1.0 (2019-10-21)

Features

  • debug: allow debugging an array of containers (88cee6f)

v4.0.0

09 Oct 11:24
c4eacd2
Compare
Choose a tag to compare

4.0.0 (2019-10-09)

Features

BREAKING CHANGES

  • baseElement is no longer tied to the document body, and container is no longer the parent node of the element wrapper, but a wrapper div.

These changes shouldn't affect you if you weren't relying on either baseElement or container.

v3.0.0

19 Aug 08:37
Compare
Choose a tag to compare

3.0.0 (2019-08-19)

Features

  • cleanup: automatically cleanup if afterEach is detected (#80) (394bde7), closes #77

BREAKING CHANGES

  • cleanup: If your tests were not isolated before (and you referenced the same component between tests) then this change will break your tests. You should keep your tests isolated, but if you're unable/unwilling to do that right away, then you can run your tests with the environment variable VTL_SKIP_AUTO_CLEANUP set to true.

v2.1.0

18 Aug 21:18
297c1c1
Compare
Choose a tag to compare

2.1.0 (2019-08-18)

Features

Support for functional components

13 Aug 09:14
08500e4
Compare
Choose a tag to compare

#41 Added support for template-only functional SFC components