|
27 | 27 | <hr /> |
28 | 28 |
|
29 | 29 | <!-- prettier-ignore-start --> |
30 | | -[![Build Status][build-badge]][build] |
31 | 30 | [![Coverage Status][coverage-badge]][coverage] |
32 | 31 | [![GitHub version][github-badge]][github] |
33 | 32 | [![npm version][npm-badge]][npm] |
@@ -66,7 +65,7 @@ npm install --save-dev @testing-library/vue |
66 | 65 | ``` |
67 | 66 |
|
68 | 67 | This library has `peerDependencies` listings for `Vue 3` and |
69 | | -`vue-template-compiler`. |
| 68 | +`@vue/compiler-sfc`. |
70 | 69 |
|
71 | 70 | You may also be interested in installing `jest-dom` so you can use [the custom |
72 | 71 | Jest matchers][jest-dom]. |
@@ -129,7 +128,7 @@ test('increments value on click', async () => { |
129 | 128 |
|
130 | 129 | > You might want to install [`jest-dom`][jest-dom] to add handy assertions such |
131 | 130 | > as `.toBeInTheDocument()`. In the example above, you could write |
132 | | -> `expect(screen.queryByText('Times clicked: 0')).toBeInTheDocument()`. |
| 131 | +> `expect(screen.getByText('Times clicked: 0')).toBeInTheDocument()`. |
133 | 132 | |
134 | 133 | > Using `byText` queries it's not the only nor the best way to query for |
135 | 134 | > elements. Read [Which query should I use?][which-query] to discover |
@@ -243,8 +242,6 @@ instead of filing an issue on GitHub. |
243 | 242 | [](https://github.com/ITenthusiasm) |
244 | 243 |
|
245 | 244 | <!-- prettier-ignore-start --> |
246 | | -[build-badge]: https://img.shields.io/github/workflow/status/testing-library/vue-testing-library/validate?logo=github |
247 | | -[build]: https://github.com/testing-library/vue-testing-library/actions?query=workflow%3Avalidate |
248 | 245 | [coverage-badge]: https://img.shields.io/codecov/c/github/testing-library/vue-testing-library.svg |
249 | 246 | [coverage]: https://codecov.io/github/testing-library/vue-testing-library |
250 | 247 | [github-badge]: https://badge.fury.io/gh/testing-library%2Fvue-testing-library.svg |
|
0 commit comments