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

@1pone/ant-design-testing

v1.0.0

Published

Easier testing for ant-design-based UI library with Jest and Vitest support

Readme

Easier testing for ant-design-based UI library with Jest and Vitest support

This library is based on React-Testing-Library and supports both Jest and Vitest testing frameworks

Usage

The latest package supports antd v5.x version. If you are using antd 4.x, please install [email protected] version.

$ npm install ant-design-testing -D
#or
$ yarn add ant-design-testing -D
#or
$ pnpm add ant-design-testing -D

Then, configure the library in your test setup file:

// setupTests.ts
import { provider } from 'ant-design-testing';

// Configure prefix class (default: 'ant')
// Configure test framework (default: 'jest')
provider({ 
    prefixCls: 'ant',
    testFramework: 'jest' // or 'vitest'
});

For Jest Users

No additional setup required. The library defaults to Jest compatibility.

For Vitest Users

Configure Vitest in your setup:

// setupTests.ts
import { provider } from 'ant-design-testing';

provider({ 
    prefixCls: 'ant',
    testFramework: 'vitest'
});

Or create a vitest.config.js:

import { defineConfig } from 'vitest/config';

export default defineConfig({
    test: {
        environment: 'jsdom',
        setupFiles: ['./tests/setupTests.ts'],
        globals: true,
    },
});

Basic Usage

// yourInput.test.tsx
import { input, testFn } from 'ant-design-testing';

describe("Test input's fire functions", () => {
    test('fireChange', () => {
        const fn = testFn(); // Framework-agnostic mock function
        const { container } = render(<Input onChange={fn} />);
        input.fireChange(container, 'test');
        expect(fn).toBeCalled();
    });
});

Otherwise, you can use query to find ant-design element quickly, like this

// yourInput.test.tsx
import { input } from 'ant-design-testing';

test('query', () => {
    const { container } = render(<div>
        <Input />
        <Input id='test' />
    </div>);
    const el = input.query(container, 1)
    expect(el.id).toBe('test');
});

A simple example form demo, like this

// your form Component
const MyForm = ({ onSubmit }: any) => {
    const [form] = Form.useForm();
    return (
        <Form form={form}>
            <Form.Item name="username">
                <Input />
            </Form.Item>
            <Form.Item name="password">
                <Input type="password" />
            </Form.Item>
            <Form.Item name="role">
                <Select>
                    <Select.Option value="admin">管理员</Select.Option>
                </Select>
            </Form.Item>
            <Button
                htmlType="submit"
                onClick={() => {
                    onSubmit(form.getFieldsValue());
                }}
            >
                提交
            </Button>
        </Form>
    );
};
// your test file
import { select, input, button, testFn } from 'ant-design-testing';

it('test MyForm', () => {
    const fn = testFn(); // Framework-agnostic mock function
    const { container } = render(
        <MyForm onSubmit={fn}/>
    );
    const userName = input.query(container)!;
    const password = input.query(container, 1)!;
    input.fireChange(userName, 'zhangsan')
    input.fireChange(password, '123456')

    select.fireOpen(container);
    select.fireSelect(document.body, 0)

    button.fireClick(container);

    expect(fn).toBeCalledWith({username: 'zhangsan', password: '123456', role: 'admin'});
});

All query methods support chain calling

// basic usage
const userName = input.query(container)!;
const password = input.query(container, 1)!;
input.fireChange(userName, 'zhangsan');
input.fireChange(password, '123456');

// chain usage
input.query(container)?.fireChange('zhangsan');
input.query(container, 1)?.fireChange('123456');

Test Framework Agnostic APIs

The library provides framework-agnostic APIs that work with both Jest and Vitest:

Mock Functions

import { testFn } from 'ant-design-testing';

const mockFn = testFn(); // Works with both Jest and Vitest

Timer Control

import { useFakeTimers, useRealTimers, runAllTimers, advanceTimersByTime } from 'ant-design-testing';

// Setup fake timers
useFakeTimers();

// Advance timers
runAllTimers();
advanceTimersByTime(1000);

// Restore real timers
useRealTimers();

Spy Functions

import { spyOn } from 'ant-design-testing';

const spy = spyOn(console, 'log');

Migration from Jest-only Code

If you have existing Jest-specific code, you can use our migration script:

npm run migrate-tests

This script will automatically update your test files to use framework-agnostic APIs.

Framework Configuration

Jest Configuration (jest.config.js)

module.exports = {
    setupFilesAfterEnv: ['./tests/setupTests.ts'],
    testEnvironment: 'jsdom',
    // ... other Jest config
};

Vitest Configuration (vitest.config.js)

import { defineConfig } from 'vitest/config';

export default defineConfig({
    test: {
        environment: 'jsdom',
        setupFiles: ['./tests/setupTests.ts'],
        globals: true,
    },
});

Running Tests

# Run with Jest
npm run test:jest

# Run with Vitest
npm run test:vitest

# Default (Jest)
npm test