archive-gh-me/vitest
1
0
Fork 0
mirror of https://github.com/vitest-dev/vitest.git synced 2026-02-01 17:36:51 +00:00
Code Issues Projects Releases Wiki Activity

docs: minor edits (#808)

Browse Source
This commit is contained in:
patak 2022-02-20 07:21:52 +01:00 committed by GitHub
parent 2e1e9c3d42
commit e75e2e539d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guide/comparisons.md
View File

@ -12,7 +12,7 @@
Cypress is known as an end-to-end testing tool, however their [new component test runner](https://on.cypress.io/component) has great support for testing Vite components and is an ideal choice to test anything that renders in a browser.
Browser-based runners, like Cypress and Web Test, will catch issues that Vitest cannot because they use the real browser and real browser APIs.
Browser-based runners, like Cypress and Web Test Runner, will catch issues that Vitest cannot because they use the real browser and real browser APIs.
Cypress's test driver is focused on determining if elements are visible, accessible, and interactive. Cypress is purpose-built for UI development and testing and its DX is centered around test driving your visual components. You see your component rendered alongside the test reporter. Once the test is complete, the component remains interactive and you can debug any failures that occur using your browser devtools.

4
docs/guide/features.md
View File

@ -21,7 +21,7 @@ Vitest smartly searches the module graph and only rerun the related tests (just
## Smooth integration with UI Frameworks
Components testing for Vue, React, Lit and more
Components testing for Vue, React, Svelte, Lit and more
## Common web idioms out-of-the-box
@ -76,7 +76,7 @@ beforeAll(async () => { ... }, 1000)
### Skipping suites and tests
Use `.skip` alias `it` to avoid running certain suites or tests
Use `.skip` to avoid running certain suites or tests
```ts
import { describe, assert, it } from 'vitest';

4
docs/src/components/FeaturesList.vue
View File

@ -7,7 +7,7 @@
<ListItem><a target="_blank" href="https://vitejs.dev">Vite</a>'s config, transformers, resolvers, and plugins.</ListItem>
<ListItem>Use the same setup from your app to run the tests!</ListItem>
<ListItem><a href="https://twitter.com/antfu7/status/1468233216939245579" target="_blank">Smart & instant watch mode, like HMR for tests!</a></ListItem>
<ListItem>Components testing for Vue, React, Lit and more</ListItem>
<ListItem>Components testing for Vue, React, Svelte, Lit and more</ListItem>
<ListItem>Out-of-box TypeScript / JSX support</ListItem>
<ListItem>ESM first, top level await</ListItem>
<ListItem>Workers multi-threading via <a href="https://github.com/Aslemammad/tinypool" target="_blank">tinypool</a></ListItem>
@ -15,7 +15,7 @@
<ListItem><a target="_blank" href="https://jestjs.io/docs/snapshot-testing" rel="nofollow">Jest Snapshot</a></ListItem>
<ListItem><a target="_blank" href="https://www.chaijs.com/" rel="nofollow">Chai</a> built-in for assertions + <a href="https://jestjs.io/docs/expect" rel="nofollow">Jest expect</a> compatible APIs</ListItem>
<ListItem><a target="_blank" href="https://github.com/Aslemammad/tinyspy" rel="nofollow">Tinyspy</a> built-in for mocking</ListItem>
<ListItem><a target="_blank" href="https://github.com/jsdom/jsdom">jsdom</a> or <a target="_blank" href="https://github.com/capricorn86/happy-dom">happy-dom</a> for DOM mocking</ListItem>
<ListItem><a target="_blank" href="https://github.com/capricorn86/happy-dom">happy-dom</a> or <a target="_blank" href="https://github.com/jsdom/jsdom">jsdom</a> for DOM mocking</ListItem>
<ListItem>Native code coverage via <a target="_blank" href="https://github.com/bcoe/c8">c8</a></ListItem>
</ul>
</template>