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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@samsara-dev/react-native-testify

v0.2.1

Published

Component-level visual regression testing for React Native

Readme

react-native-testify

Component-level visual regression testing for React Native. Mount components in isolation, capture screenshots, and detect UI changes.

Note: This library requires Bun runtime for the CLI.

Features

  • Isolated Component Rendering - Test components without building the full app
  • Visual Regression Testing - Compare screenshots against baselines using pixelmatch
  • Provider Support - Wrap components with Redux, Theme, or any context providers
  • Idle Detection - Automatically wait for JS thread idle before capturing screenshots
  • Per-Component Config - Custom wait times, async conditions per component
  • Auto-Discovery - Discover *.testify.tsx files and generate registry automatically
  • Parallel Testing - Run tests on iOS and Android simultaneously
  • Retry Logic - Configurable retries for flaky renders

How It Works

flowchart TB
    subgraph Development
        A[Component Code] --> B[*.testify.tsx]
        B --> |bunx testify discover| C[Generated Registry]
    end
    
    subgraph Runtime
        C --> D[TestifyApp]
        D --> E[Mount Component]
        E --> F[Wait for Idle]
        F --> G[Capture Screenshot]
    end
    
    subgraph Testing
        G --> |record| H[Baseline Image]
        G --> |test| I[Compare with Baseline]
        I --> J{Match?}
        J --> |Yes| K[✓ Pass]
        J --> |No| L[✗ Fail + Diff]
    end

Architecture: Testify requires a native binary build (like any visual testing solution), but instead of rendering your full app tree, the TestifyApp harness mounts components in isolation. Each component is wrapped with your providers (Theme, Redux, etc.) and rendered one at a time - no navigation, no other screens, just the component under test.

Workflow Demo

https://github.com/user-attachments/assets/f794629e-62e1-406c-90e4-078fe586842a

Requirements

  • Bun >= 1.0.0 (for CLI)
  • React Native >= 0.65.0
  • Xcode (for iOS Simulator)
  • Android Studio (for Android Emulator)

Installation

bun add @samsara-dev/react-native-testify

Quick Start

1. Create component testify files

// src/components/Button.testify.tsx
import { Button } from './Button';

export default {
  'Button/Primary': {
    render: () => <Button variant="primary" title="Click me" />,
  },
  'Button/Disabled': {
    render: () => <Button disabled title="Disabled" />,
  },
};

2. Create config file

// testify.config.ts
import { defineConfig } from '@samsara-dev/react-native-testify/config';

export default defineConfig({
  baselines: './testify/baselines',
  threshold: 0.01,
  discovery: {
    enabled: true,
    pattern: '**/*.testify.tsx',
    rootDir: './src',
  },
  ios: {
    simulator: 'iPhone 15 Pro',
    bundleId: 'com.yourapp',
  },
});

3. Generate registry and create entry point

bunx testify discover
// index.testify.js
import { AppRegistry } from 'react-native';
import { TestifyApp } from '@samsara-dev/react-native-testify';
import registry from './testify/.generated-registry';
import { ThemeProvider } from './src/theme';

const App = () => (
  <TestifyApp
    registry={registry}
    providers={[{ component: ThemeProvider }]}
  />
);
AppRegistry.registerComponent('YourApp', () => App);

4. Run tests

# Record baseline screenshots
bunx testify record --ios

# Run visual regression tests
bunx testify test --ios

# Run tests on Android
bunx testify test --android

# Run parallel tests on iOS + Android simultaneously
bunx testify test --all

# Update specific baselines
bunx testify update Button_Primary --ios

Auto-Discovery Mode

Instead of a central registry, you can create per-component testify files:

1. Enable discovery in config

// testify.config.ts
export default defineConfig({
  discovery: {
    enabled: true,
    pattern: '**/*.testify.tsx',
    rootDir: './src',
    generatedRegistry: './testify/.generated-registry.tsx',
  },
});

2. Create component testify files

// src/components/Button.testify.tsx
import { Button } from './Button';

export default {
  'Button/Primary': {
    render: () => <Button variant="primary" title="Click me" />,
  },
  'Button/Secondary': {
    render: () => <Button variant="secondary" title="Click me" />,
  },
  'Button/Disabled': {
    render: () => <Button disabled title="Disabled" />,
  },
};

3. Generate registry

bunx testify discover

4. Use generated registry with providers

// index.testify.js
import { AppRegistry } from 'react-native';
import { TestifyApp } from '@samsara-dev/react-native-testify';
import registry from './testify/.generated-registry';
import { ThemeProvider } from './src/theme';

// Pass providers/wrapper as props to TestifyApp
const App = () => (
  <TestifyApp
    registry={registry}
    providers={[{ component: ThemeProvider, props: {} }]}
    wrapper={(children) => <View style={styles.container}>{children}</View>}
  />
);

AppRegistry.registerComponent('YourApp', () => App);

Idle Detection

By default, screenshots are taken when the JS thread becomes idle (using React Native's InteractionManager), rather than waiting a fixed time. This makes tests faster and more reliable.

Configure in your config or per-component:

// testify.config.ts
export default defineConfig({
  idleDetection: {
    enabled: true,      // default
    timeoutMs: 5000,    // max wait before timeout
    debounceMs: 100,    // stability debounce
  },
});

To disable and use fixed wait times:

idleDetection: {
  enabled: false,
},
defaultWaitMs: 500,

Registry API

Simple components

createRegistry({
  'ComponentName': () => <YourComponent />,
});

With custom wait time

createRegistry({
  'SlowComponent': {
    render: () => <SlowComponent />,
    waitMs: 2000,
  },
});

With async waitFor

createRegistry({
  'AsyncComponent': {
    render: () => <DataFetcher />,
    waitFor: async () => {
      await someAsyncCondition();
    },
  },
});

With providers

createRegistry({
  'Button': () => <Button />,
}, {
  wrapper: (children) => (
    <ReduxProvider store={store}>
      <ThemeProvider>
        {children}
      </ThemeProvider>
    </ReduxProvider>
  ),
});

With store isolation

createRegistry({
  'Component': {
    render: () => <Component />,
    freshStore: true,  // Get fresh store for this component
  },
}, {
  storeFactory: () => createStore(),
  storeIsolation: true,  // Enable globally
});

Configuration

| Option | Type | Default | Description | |--------|------|---------|-------------| | entry | string | ./index.testify.js | Testify entry point | | registry | string | ./testify/registry.tsx | Registry file path | | baselines | string | ./testify/baselines | Baseline screenshots directory | | threshold | number | 0.01 | Diff threshold (0-1) for pass/fail and pixelmatch sensitivity | | defaultWaitMs | number | 500 | Default render wait time (when idle detection disabled) | | retryCount | number | 2 | Retry attempts for flaky tests | | retryDelayMs | number | 1000 | Delay between retries | | port | number | 8089 | WebSocket server port | | gitLfs | boolean | false | Enable git-lfs tracking hint |

iOS Config

ios: {
  simulator: 'iPhone 15 Pro',
  scheme: 'YourApp',
  workspace: 'ios/YourApp.xcworkspace',
  bundleId: 'com.yourapp',
  viewport: { width: 393, height: 852 },
}

Android Config

android: {
  emulator: 'Pixel_7_API_34',
  packageName: 'com.yourapp',
  projectDir: 'android',
  gradleTask: 'assembleDebug',
  viewport: { width: 412, height: 915 },
}

Status Bar

Freeze status bar for consistent screenshots:

statusBar: {
  freeze: true,  // default
}

Discovery Config

discovery: {
  enabled: false,
  pattern: '**/*.testify.tsx',
  exclude: ['node_modules', 'dist', '.git', 'ios', 'android'],
  generatedRegistry: './testify/.generated-registry.tsx',
}

Idle Detection Config

idleDetection: {
  enabled: true,
  timeoutMs: 5000,
  debounceMs: 100,
}

CLI Commands

bunx testify init              # Initialize testify in project
bunx testify build             # Build the app for testing
bunx testify record --ios      # Record baseline screenshots
bunx testify test --ios        # Run visual regression tests
bunx testify test --android    # Test on Android
bunx testify test --all        # Parallel iOS + Android
bunx testify update <name>     # Update specific baseline
bunx testify list              # List registered components
bunx testify discover          # Discover *.testify.tsx files

# Options
--ios                        # Target iOS simulator
--android                    # Target Android emulator
--all                        # Target both iOS and Android (parallel)
--parallel                   # Run tests in parallel on multiple devices
--filter <pattern>            # Filter components (glob pattern)
--watch, -w                   # Watch mode
--config <path>               # Path to config file
--dry-run                     # Preview without writing (discover)
--verbose, -v                 # Show detailed output

Parallel Testing

Run tests on both platforms simultaneously:

bunx testify test --all

Output:

┌─ Button_Primary
│  [ios] ✓ Pass
│  [android] ✓ Pass
└─

┌─ Card_Simple
│  [ios] ✓ Pass
│  [android] ✗ 0.42% diff
└─

Results: 3 passed, 1 failed

Baselines are stored per-platform:

testify/baselines/
├── ios/
│   ├── Button_Primary.png
│   └── Card_Simple.png
└── android/
    ├── Button_Primary.png
    └── Card_Simple.png

How It Works

  1. Start Metro with testify entry point
  2. CLI launches simulator/emulator and connects via WebSocket
  3. For each component:
    • CLI sends mount command
    • App renders component and waits for idle (or fixed time)
    • App signals ready
    • CLI captures screenshot via xcrun simctl (iOS) or adb (Android)
    • CLI sends unmount command
  4. Compare screenshots against baselines using pixelmatch
  5. Report pass/fail with diff images for failures

Git LFS for Baselines

Large baseline images can bloat your repo:

git lfs install
git lfs track "testify/baselines/**/*.png"

License

MIT