Skip to content

Commit a531cdc

Browse files
fix: removed the unnecessary explanation
1 parent bd701ca commit a531cdc

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

src/guide/scaling-up/testing.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Take for example this `increment` function:
4040

4141
```js
4242
// helpers.js
43-
export function increment(current, max = 10) {
43+
export function increment (current, max = 10) {
4444
if (current < max) {
4545
return current + 1
4646
}
@@ -186,13 +186,9 @@ mount(Stepper, {
186186
}
187187
})
188188

189-
cy.get(valueSelector)
190-
.should('be.visible')
191-
.and('contain.text', '0')
192-
.get(buttonSelector)
193-
.click()
194-
.get(valueSelector)
195-
.should('contain.text', '1')
189+
cy.get(valueSelector).should('be.visible').and('contain.text', '0')
190+
.get(buttonSelector).click()
191+
.get(valueSelector).should('contain.text', '1')
196192
```
197193

198194
</div>
@@ -223,9 +219,9 @@ Component testing often involves mounting the component being tested in isolatio
223219

224220
- [`@vue/test-utils`](https://github.com/vuejs/test-utils) is the official low-level component testing library that was written to provide users access to Vue specific APIs. It's also the lower-level library `@testing-library/vue` is built on top of.
225221

226-
- [`@testing-library/vue`](https://github.com/testing-library/vue-testing-library) is a Vue testing library focused on testing components without relying on implementation details. Built with accessibility in mind, its approach also makes refactoring a breeze. Its guiding principle is that the more tests resemble the way software is used, the more confidence they can provide.
222+
- [`@testing-library/vue`](https://github.com/testing-library/vue-testing-library) is a Vue testing library focused on testing components without relying on implementation details. Its guiding principle is that the more tests resemble the way software is used, the more confidence they can provide.
227223

228-
We recommend using `@vue/test-utils` for testing components in applications, as its focus aligns better with the testing priorities of applications. `@testing-library/vue` has issues with testing asynchronous component with Suspense, so it should be used with caution.
224+
We recommend using `@vue/test-utils` for testing components in applications. `@testing-library/vue` has issues with testing asynchronous component with Suspense, so it should be used with caution.
229225

230226
### Other Options {#other-options-1}
231227

0 commit comments

Comments
 (0)