/handbook/react-best-practices/testing/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources React project best practices Testing
Topics
On this page
- React project best practices
- Project structure
- State management
- Component architecture
- Styling
- Hooks
- Performance optimization
- Commit messages
- Code quality
- Data loading
- Testing
- Dependency management
- Accessibility
- React frameworks
- Documentation
- Deployment and monitoring
- React skeleton
- Appendices
1. Testing philosophy
Test user behavior, not implementation details
Write tests that survive refactoring
Mock at the boundaries, not within the application
Structure tests with AAA ("Arrange, Act, Assert")
Prioritize accessible queries
2. Testing levels
Unit tests (base)
Integration tests (middle)
End-to-end tests (top)
3. Additional best practices
Key takeaways
Last updated on Apr 2, 2026
Testing
Testing is not just about verifying that code works. It’s about ensuring that applications remain reliable, maintainable, and accessible as they evolve. Good tests are resilient to refactoring, mirror real user behavior, and provide confidence without slowing down development.
1. Testing philosophy
Test user behavior, not implementation details
- Focus on what users see and do, not internal component structures.
- Avoid testing state variables, class names, or DOM structure unless absolutely necessary.
Good example (behavior-driven)
// Simulates the user finding a button by its visible name and clicking it.
import { render, screen, fireEvent } from '@testing-library/react';
test('should submit the form when the button is clicked', () => {
render();
const submitButton = screen.getByRole('button', { name: /submit/i });
fireEvent.click(submitButton);
// Assert that the form was submitted
});
Bad example (brittle test)
// This test will break if styles change or the implementation is refactored.
const { container } = render(<MyComponent />);
// This test would fail if you switched from CSS modules to Tailwind.
expect(container.querySelector('.submit-button-style')).toBeInTheDocument();
Write tests that survive refactoring
This is the direct benefit of testing behavior over implementation.
A good test should only fail for two reasons:
- Functionality is intentionally changed. (and the test needs to be updated).
- Functionality is accidentally broken (a regression).
A test should not fail if you refactor the code, like renaming a state variable, switching from a <div> to a <section>, or changing a CSS class name, while keeping the user-facing behavior identical.
Mock at the boundaries, not within the application
- Mock external dependencies (APIs, service workers, network requests).
- Avoid mocking internal application modules or functions. If you mock a function that Component A imports from
utils.js, your test is now coupled to the internal architecture of your app, not its behavior. - A For example
fetchcalls orservice workercalls are such interfaces.
Structure tests with AAA (“Arrange, Act, Assert”)
This pattern (also known as “Given, When, Then”) makes tests drastically easier to read and understand. Every test should have three distinct parts:
- Arrange: Set up the test. Render the component, find the elements, and prepare any mock data.
- Act: Perform the user action you are testing (e.g., click a button, type in a form).
- Assert: Check the outcome. Did the component behave as expected after the action?
test('should show an error message when the form is submitted with an invalid email', () => {
// Arrange
render();
const emailInput = screen.getByLabelText(/email/i);
const submitButton = screen.getByRole('button', { name: /submit/i });
// Act
fireEvent.change(emailInput, { target: { value: 'invalid-email' } });
fireEvent.click(submitButton);
// Assert
const errorMessage = screen.getByText(/please enter a valid email address/i);
expect(errorMessage).toBeInTheDocument();
});
Prioritize accessible queries
The Testing Library query API is organized by accessibility priority. By following this priority, you not only write more robust tests but you also build more accessible applications. If your component is hard to test with accessible queries, it’s likely hard for users with assistive technologies to use.
The Priority Order:
- Queries accessible to everyone:
getByRole,getByLabelText,getByPlaceholderText,getByText,getByDisplayValue. - Semantic Queries:
getByAltText,getByTitle. - Test ID:
getByTestId(Use this as a last resort when you can’t match by role or text).
2. Testing levels
Unit tests (base)
Fast, isolated tests for individual functions, components, or hooks. For UI components, Storybook is recommended. For functions and hooks Vitest is recommended.
Writing stories for UI components is important. It provides a directory of components for easy lookup. The components can also be tested individually with manual or automated means.
- Verify visuals: Quickly see if the component renders correctly across all its states.
- Test interactivity: Use the Controls addon to tweak props in real-time and see how the component responds.
- Check responsiveness: Use the Viewport addon to see how the component looks on different screen sizes (mobile, tablet, desktop).
- Explore edge cases: Manually input weird data or long strings into props to see if the layout breaks.
Integration tests (middle)
- Test how multiple components work together, often involving user interactions within a subset of the application. For example, a form composed of different input elements will be considered a unit test.
- Integration testing are setup up similar to unit testing with the possible exception of setup requirements. The setup requirements may include hydrating initial state and mocking APIs.
End-to-end tests (top)
- Simulate real user flows in a browser (e.g., login > dashboard > logout)..
- Since these tests are expensive, cover only critical paths.
- These kinds of tests are generally done with browser emulation and dev servers and should not require any kind of mocking.
- We recommend using
Playwrightfor running these kinds of tests. Along with the usual Assertion/Snapshot based tests, We also recommend adding visual comparisons to test for any visual regressions.
Playwrightalso provides integrations with axe-core for testing accessibility. For a more comprehensive assessment of Web Content Accessibility Guidelines (WCAG) 2.1 Level AA , axe accessibility testing engine is recommended.- Ensure compliance with WCAG 2.1 AA.
3. Additional best practices
-
Test pyramid balance
- More unit tests > fewer integration tests > minimal but critical E2E tests.
-
Accessibility testing
- Integrate axe-core in both E2E and Storybook environments.
-
CI integration
- Run tests automatically in CI (GitHub Actions, GitLab CI, etc.).
- Fail builds on test failures or accessibility violations.
-
Coverage tracking
- Use
vitest --coverage(or Jest equivalent). - Set minimum thresholds (e.g., 80%) but prioritize meaningful coverage over numbers.
- Use
Key takeaways
- Write tests that reflect user behavior, not implementation.
- Structure tests with Arrange, Act, Assert for clarity.
- Mock only at boundaries (APIs, services).
- Balance unit, integration, and E2E tests to optimize speed and reliability.
- Use tools like Playwright + axe-core for end-to-end and accessibility testing.
- Ensure tests are part of CI/CD, preventing regressions before they reach production.
Do check out our handbook on Quality Engineering.
Credits
Sayed Taqui
Author
Sayed Taqui
Author
Seasoned React, JavaScript, and WordPress Developer. Contributed significantly to WordPress Core. Currently serving as the Lead WordPress Engineer at rtCamp. Passionate about crafting innovative so…
Imran Sayed
Author
Imran Sayed
Author
Senior Software Engineer and Full-Stack Web Developer building high-performance, user-centric web applications that drive business growth. Expertise lies in e-commerce development, custom WordPress…
Ayush Nirwal
Author
Ayush Nirwal
Author
Amoghavarsha Kudaligi
Author
Amoghavarsha Kudaligi
Author
Mayank Rana
Author
Mayank Rana
Author
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept