Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[docs]: remove duplicate sentence #1936

Merged
merged 1 commit into from Jan 10, 2023
Merged

[docs]: remove duplicate sentence #1936

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guide/essentials/easy-to-test.md
View file
Open in desktop
Expand Up @@ -28,7 +28,7 @@ Notice how this list does not include elements such as internal methods, interme

The rule of thumb is that **a test should not break on a refactor**, that is, when we change its internal implementation without changing its behavior. If that happens, the test might rely on implementation details.

For example, let's assume a basic Counter component that features a button to increment a counter. We could write the following test:
For example, let's assume a basic Counter component that features a button to increment a counter:

```vue
<template>
Expand Down