Devtools, Testing and Debugging Learn to diagnose cache behavior instead of fighting it
Phase 22 - TanStack Query Volume 06 - Professional Frontend
Devtools make the invisible cache visible During development, React Query Devtools lets you inspect query keys, status, observers, freshness and cached data. It is especially useful when a query “does not refetch” or “refetches too much.”
Debug in this order Symptom First questions
Wrong list appears Does queryKey include every input used by queryFn?
Refetches constantly What is staleTime? Is focus refetch expected?
Mutation succeeds but UI old Was the correct key family invalidated?
Pagination flashes empty Use placeholderData / keepPreviousData?
401 repeats Is retry disabled for auth failures?
Different user sees old data Was QueryClient cleared on auth transition?
Test the contract, not the library Component tests should verify loading, success, error and mutation behavior. Query-option tests can verify key shape. End-to-end tests should prove a successful mutation eventually produces the correct server-backed UI. Avoid writing tests that merely reproduce TanStack Query internals.
// Example key-level assertion expect(taskKeys.list({ page: 2, pageSize: 20 })).toEqual([ "tasks", "list", { page: 2, pageSize: 20 }, ]);
Useful development checks Open Devtools, navigate page 1 -> page 2 -> page 1 and observe cache reuse. Trigger a create mutation and observe list queries become invalidated. Refocus the browser after staleTime expires and watch background fetching without losing the previous successful table.
When data looks unexpectedly shared or stale, inspect the query key before adding manual refetch calls. Manual refetch often hides a poorly modeled key rather than fixing it.
Tests are executable behavioral contracts. Good tests protect meaningful invariants and failure cases, not implementation trivia.
Restate the goal of “Devtools Testing and Debugging” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: behavior contract → arrange → act → assert → regression signal. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: TaskFlow query/mutation layer with stable keys, list/detail caching, invalidation, filters, and debugging via devtools/logs.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
it("rejects deleting another member's task", async () => {
const response = await asUser(bob).delete(`/tasks/${aliceTask.id}`);
expect(response.status).toBe(403);
expect(await taskStillExists(aliceTask.id)).toBe(true);
});Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Look for shared database state, timers, globals, unordered execution, or missing cleanup before adding retries.
Move the highest-risk boundary to an integration test with the real adapter/database.
Without copying the final source, create a second small scenario that applies “Devtools Testing and Debugging” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Implement create/update mutations and choose between invalidation and direct cache updates deliberately.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Invalidating too broadly or not at all
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.