英文:
SWR Test Mutation
问题
以下是您要翻译的内容：
What is a recommended way of testing mutation from SWR?
const { data, mutate } = useSWR("/api/user", fetch);if (data.loggedIn) {return (<ButtononClick={() => {logout();mutate(); // after logging in/out, we mutate the SWR}}>Logout</Button>);} else {// loginreturn (<h1>Please login</h1>)}}```Related to discussion: https://github.com/vercel/swr/discussions/2434If we have given flow `logout -> mutate swr -> show login form`I think we shouldn't test implementation details and instead test what user actually see after mutation/change happened?```expect(mutate).toHaveBeenCalled('/logout'); // badexpect(screen.getByText('Please login')).toBeInTheDocument(); // correct```What is the general feeling about this?<details><summary>英文:</summary>What is a recommended way of testing mutation from SWR?
function Index() {
const { data, mutate } = useSWR("/api/user", fetch);
if (data.loggedIn) {
return (
<Button
onClick={() => {
logout();
mutate(); // after logging in/out, we mutate the SWR
}}
>
Logout
</Button>
);
} else {
// login
return (<h1>Please login</h1>)
}
}
Related to discussion: https://github.com/vercel/swr/discussions/2434If we have given flow `logout -> mutate swr -> show login form`I think we shouldn't test implementation details and instead test what user actually see after mutation/change happened?
expect(mutate).toHaveBeenCalled('/logout'); // bad
expect(screen.getByText('Please login')).toBeInTheDocument(); // correct
What is the general feeling about this?</details># 答案1**得分**: 0这应该可以工作，但是你可能要考虑模拟`fetch`而不是`mock fetch`。```javascriptimport { useSWRConfig } from 'swr';// FIXME: tests should be mocking the fetch instead// https://dev.to/bmvantunes/please-don-t-mock-swr-fetch-or-axios-in-your-unit-integration-tests-521kjest.mock('swr', () => ({...jest.requireActual('swr'),useSWRConfig: jest.fn(() => ({mutate: () => {},})),}));it('should mutate data', async () => {const mockMutate = jest.fn();useSWRConfig.mockImplementationOnce(() => ({ mutate: mockMutate }));expect(mockMutate).toHaveBeenCalledWith('swrKey');...});
英文:
This should work, however you want to consider to mock the fetch instead.
import { useSWRConfig } from 'swr';// FIXME: tests should be mocking the fetch instead// https://dev.to/bmvantunes/please-don-t-mock-swr-fetch-or-axios-in-your-unit-integration-tests-521kjest.mock('swr', () => ({...jest.requireActual('swr'),useSWRConfig: jest.fn(() => ({mutate: () => {},})),}));it('should mutate data', async () => {const mockMutate = jest.fn();useSWRConfig.mockImplementationOnce(() => ({ mutate: mockMutate }));expect(mockMutate).toHaveBeenCalledWith('swrKey');...});
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论