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.

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

docs: fix fragment links in testing stores page #2351

Merged
merged 2 commits into from
Aug 15, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 1 addition & 12 deletions packages/docs/cookbook/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,18 +6,7 @@ Stores will, by design, be used at many places and can make testing much harder
- `actions`: most of the time, they contain the most complex logic of our stores. Wouldn't it be nice if they were mocked by default?
- Plugins: If you rely on plugins, you will have to install them for tests too

Depending on what or how you are testing, we need to take care of these three differently:

- [Testing stores](#testing-stores)
- [Unit testing a store](#unit-testing-a-store)
- [Unit testing components](#unit-testing-components)
- [Initial State](#initial-state)
- [Customizing behavior of actions](#customizing-behavior-of-actions)
- [Specifying the createSpy function](#specifying-the-createspy-function)
- [Mocking getters](#mocking-getters)
- [Pinia Plugins](#pinia-plugins)
- [E2E tests](#e2e-tests)
- [Unit test components (Vue 2)](#unit-test-components-vue-2)
Depending on what or how you are testing, we need to take care of these three things differently.

## Unit testing a store

Expand Down
Loading