npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@atomic-testing/react-legacy

v0.78.0

Published

Adapter for testing React 17 and earlier

Readme

@atomic-testing/react-legacy

Adapter for integrating Atomic Testing with React 16/17. It maps React components to the core scene part APIs.

The problem

Writing maintainable tests for UIs built with third–party component libraries like Material UI or Bootstrap can be tricky. Documentation on how a test should communicate with these components is often lacking, so tests easily end up coupled to implementation details. As your application grows you need your tests to scale without constantly reworking them.

The solution

Atomic Testing provides a consistent way to interact with both third–party and first–party components across different test environments. It focuses on reusability, composability and adaptability, letting you build higher–level test strategies that work for DOM or end–to–end testing alike.

Installation

npm install @atomic-testing/core @atomic-testing/react-legacy --save-dev

Refer to the React integration guide for examples.

Example

If you use MUI/Material UI components, have a look at the @atomic-testing/component-driver-mui-v5 package for a dedicated example.

  1. Install the core library and basic HTML drivers along with this React adapter:

    npm install @atomic-testing/core @atomic-testing/react-legacy @atomic-testing/component-driver-html --save-dev
  2. Create a small component and assign data-testid values to the elements you want to interact with:

    import { useState } from 'react';
    
    export function Counter() {
      const [count, setCount] = useState(0);
      return (
        <div>
          <span data-testid='count'>{count}</span>
          <button data-testid='increment' onClick={() => setCount(c => c + 1)}>
            Increment
          </button>
        </div>
      );
    }
  3. Define a ScenePart describing the count display and button using the HTML drivers:

    import { HTMLButtonDriver, HTMLElementDriver } from '@atomic-testing/component-driver-html';
    import { byDataTestId, ScenePart } from '@atomic-testing/core';
    
    export const counterScenePart = {
      count: { locator: byDataTestId('count'), driver: HTMLElementDriver },
      increment: { locator: byDataTestId('increment'), driver: HTMLButtonDriver },
    } satisfies ScenePart;
  4. Write a test using createTestEngine to render the component and interact with it:

     import { createTestEngine } from '@atomic-testing/react-legacy';
    
     import { Counter } from './Counter';
     import { counterScenePart } from './counterScenePart';
    
     test('increments when the button is clicked', async () => {
       const engine = createTestEngine(<Counter />, counterScenePart);
    
       expect(await engine.parts.count.getText()).toBe('0');
       await engine.parts.increment.click();
       expect(await engine.parts.count.getText()).toBe('1');
    
       await engine.cleanUp();
     });

For more in‑depth information, visit https://atomic-testing.dev.