# testing-library Published articles for testing-library. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI-assisted migration from Enzyme to React Testing Library DevFeed: [AI-assisted migration from Enzyme to React Testing Library]() Original publisher: [Read original article]() Author: Ivan Klaric Published: 2026-08-27T18:04:54Z Content type: article Language: en Sources: [The Pragmatic Engineer]() Topics: [Testing](), [migration](), [testing-library](), [Artificial Intelligence](), [OpenAI](), [codex](), [React Native]() Tags: [ai](), [codex](), [migration](), [migrations](), [openai](), [react](), [testing](), [testing-library]() ### AI overview The article examines Asana's migration from Enzyme to React Testing Library and discusses how AI-assisted coding, including OpenAI Codex, may make large testing-system migrations more practical. It compares the different testing approaches and syntax used by the two libraries. ### Source excerpt Asana migrated off testing framework Enzyme in two weeks: without AI, this work would surely have been kicked down the road. Airbnb and Uber share similar stories and AI seems excellent at migrations. ## Migrating 76,000 Tests from Enzyme to React Testing Library DevFeed: [Migrating 76,000 Tests from Enzyme to React Testing Library]() Original publisher: [Read original article]() Author: Charley Pugmire Published: 2025-11-13T18:31:47Z Content type: tutorial Language: en Sources: [HubSpot]() Topics: [testing-library](), [React](), [Testing](), [migration](), [ui-testing]() Tags: [engineering](), [migration](), [react](), [testing](), [testing-library](), [ui-testing]() ### AI overview The article explains how a team migrated more than 76,000 tests from Enzyme to React Testing Library over two and a half years. It describes the shift toward user-focused UI tests, the planning process, and the limits of using static analysis alone to estimate the work. ### Source excerpt For years, Enzyme was the de facto standard for testing React applications. Originally built by Airbnb in 2015, Enzyme makes it easy to assert, manipulate, and traverse the output of React components. The last official release of Enzyme came after React 16 was launched in 2017, but even then did not fully support all React 16 features. Ongoing support for Enzyme shifted to the open source community with React 17. However, the creator of the community-maintained Enzyme adapter announced that he would not be offering an updated version for React 18. This effectively marked the end of the Enzyme project, as it would prevent users from leveraging new features like React 18's concurrent mode. ## I got my first promotion in 10 months DevFeed: [I got my first promotion in 10 months]() Original publisher: [Read original article]() Author: Tiger Abrodi Published: 2024-04-07T13:11:46Z Content type: opinion Language: en Sources: [Saiyan Growth Letter]() Topics: [Accessibility](), [Testing](), [testing-library](), [React](), [User Experience]() Tags: [accessibility](), [axe-devtools](), [performance](), [react](), [testing-library](), [tests]() ### AI overview The author describes moving from junior to mid-level developer in 10 months. They attribute the promotion to improving website accessibility, using screen readers and Axe DevTools, sharing accessible coding practices, introducing pair reviews and a stop-and-fix practice, and documenting performance APIs in React. ### Source excerpt Sharing what I did and learned along the way ## Snapshot Testing Libraries for Android: Paparazzi vs Shot DevFeed: [Snapshot Testing Libraries for Android: Paparazzi vs Shot]() Original publisher: [Read original article]() Author: Fajar Febriyan Published: 2024-02-29T03:56:36Z Content type: comparison Language: en Sources: [astronauts-id - Medium]() Topics: [Android](), [screenshot-testing](), [Testing](), [ui-testing](), [testing-library](), [Framework]() Tags: [android](), [android-app-development](), [compare](), [comparison](), [developers](), [screenshot-testing](), [testing](), [testing-library](), [ui-testing]() ### AI overview This comparison explains snapshot testing for Android UI components and contrasts the Shot and Paparazzi libraries. It covers visual regression detection, cross-device consistency, setup, golden images, and verification. ### Source excerpt What is snapshot testing? Snapshot testing, also known as screenshot testing, is an automated testing technique that captures screenshots of User Interface (UI) components and compares them against reference images. The idea is simple: we save a reference screenshot of a UI component in a known good state, and during testing, we capture a new screenshot and compare it to the reference. If these two images match, the test passes; if not, it fails. Comparing the golden image (real pineapple) with the image (pineapple illustration)Then why snapshot testing? According to the Testing Pyramid, UI testing, also known as, end-to-end testing is a type of testing recommended to be carried out in application development. UI testing is basically a mechanism meant to test the UI aspect of any software that users come into contact with. One way to do this is with a simple concept not requiring painful scenarios which is the snapshot testing. The image above is referenced from Martin Fowler's post regarding the Test Pyramid Snapshot testing is beneficial for various reasons: Visual Regression Detection: It helps identifying unintended visual changes introduced during development. Ease of Use: Writing snapshot tests is often simpler and more intuitive than crafting complex UI test scripts. Cross-Platform Testing: Snapshot tests can be used to ensure consistency across various Android devices and configurations. Let's dive into the libraries We chose to discuss and compare these 2 libraries because they have different methods and produce different results. Shot Shot is an open-source snapshot testing library developed by Pedro Vicente Gómez Sánchez. It integrates seamlessly with popular testing frameworks like JUnit and Espresso, making it a popular choice among Android developers. Paparazzi Paparazzi is another popular snapshot testing library developed by Cash App. It offers robust screenshot comparison and supports testing on a wide range of Android devices. How it works? Setup: ## Testing API Calls With React Testing Library and Jest DevFeed: [Testing API Calls With React Testing Library and Jest]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2022-12-09T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [testing-library](), [Testing](), [React](), [API](), [Jest](), [Webpack]() Tags: [api](), [asynchronous](), [jest](), [react](), [testing](), [testing-library](), [webpack]() ### AI overview A tutorial showing how to test React useEffect API calls with Jest and React Testing Library, including tests for successful and failed requests. ### Source excerpt Ever since Hooks were released in React, we've been using the hook to fetch data, whether directly or abstracted away behind Redux Thunks... ## Testing Library ByRole Performance Improvements DevFeed: [Testing Library ByRole Performance Improvements]() Original publisher: [Read original article]() Author: Jonathan Darrer Published: 2022-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Findmypast]() Topics: [Testing](), [React](), [ui]() Tags: [improvements](), [performance](), [react](), [testing](), [testing-library](), [tests]() ### AI overview This article explains how Testing Library queries affect test performance in React UI tests. It compares role-based queries with the more limited ByText and ByLabelText queries, notes that they are not interchangeable for every assertion, and describes contextualizing queries when necessary. In the tested instances, the recommended changes improved performance from 320 ms to 16 ms, a 95% improvement. ### Source excerpt We use Testing Library to test our React UI pages and components. For example, we may have the following HelpFaqsTile component in a page: const HelpFaqsTile = () => (

Need some help?

Our FAQs are a lifesaver

 ); export default HelpFaqsTile; Let suppose we want to test whether "the 'Help Faqs' tile provides a link with the text Search FAQs": import { act, render } from '@testing-library/react'; await render( ); const buttonToFaq = screen.getByRole('link', { name: 'Search FAQs', }); expect(buttonToFaq).toBeInTheDocument(); *ByRole methods like screen.getAllByRole('link', {name: 'Search FAQs'}) can be slow due to the way in which they search through the entire DOM tree looking for nodes matching the role type, and optionally a variety of attributes (label, aria-label, etc. depending on additional criteria, here name). In contrast, the more performant *ByText and *ByLabelText methods look for text nodes and nodes with more limited attributes (label and aria-label only) respectively. So, we could use screen.getByText('Search FAQs') instead: import { act, render } from '@testing-library/react'; await render( ); const buttonToFaq = screen.getByText('Search FAQs'); expect(buttonToFaq).toBeInTheDocument(); They are not like for like replacements however. Let's suppose we want to test "the 'Help Faqs' tile provides a link which directs the user to our FAQ's" import { act, render } from '@testing-library/react'; await render( ); const buttonToFaq = screen.getByRole('link', { name: 'Search FAQs', }); expect(buttonToFaq).toBeInTheDocument(); expect(buttonToFaq).toHaveAttribute('href', '/ ## Keeping up the Open Source promise for 2021 DevFeed: [Keeping up the Open Source promise for 2021]() Original publisher: [Read original article]() Author: Patrick Gotthardt Follow Published: 2021-01-25T00:00:00Z Content type: opinion Language: en Sources: [Trivago]() Topics: [Open Source](), [Webpack](), [Preact.js](), [Front end](), [Cloud Native Ecosystem](), [Kubernetes](), [gRPC](), [Prometheus]() Tags: [community](), [company](), [frontend](), [kubernetes](), [libraries](), [open-source](), [open-source-software](), [patches](), [preact](), [prometheus](), [testing-library](), [webpack]() ### AI overview trivago describes its 2021 commitment to supporting open source projects and organizations, including webpack, Preact, and the Cloud Native Computing Foundation. It also highlights financial support, community participation, and contributions such as open source libraries and patches. ### Source excerpt COVID-19 has impacted the travel industry very severely. Even in these hard times, trivago remains committed to contributing to open source. As a tech company working on large-scale projects, we feel a responsibility towards supporting the open source community. webpack, Preact and the CNCF This year we will continue supporting projects and organisations that are having a major impact on the products we build and the happiness of our engineers who use them on a daily basis.