eigen-testing
Write and maintain tests for Eigen, a React Native application using React Native Testing Library and Relay Test Utils. Use this skill when writing new tests, fixing failing tests, adding test coverage, updating existing tests, or when asked about testing best practices for Eigen. Triggers on requests like "write tests for this component", "add test coverage", "fix this test", "how should I test this", or any testing-related questions for the Eigen codebase.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Eigen Testing Skill
Use this skill to write high-quality tests for Eigen following established patterns and best practices.
Quick Start
For Non-Relay Components
Use the template at assets/component-test-template.tsx as a starting point:
import { fireEvent, screen } from "@testing-library/react-native"
import { renderWithWrappers } from "app/utils/tests/renderWithWrappers"
For Relay Components
Use the template at assets/relay-test-template.tsx as a starting point:
import { setupTestWrapper } from "app/utils/tests/setupTestWrapper"
import { graphql } from "react-relay"
Critical Rules
-
File Location: Always place tests in
__tests__directories colocated with source files -
File Naming: Use
.tests.tsx(not.test.tsxor.spec.tsx) -
Never Use Deprecated Utilities: Avoid
renderWithWrappersLEGACY,setupTestWrapper_LEGACY,resolveMostRecentRelayOperation,flushPromiseQueue,waitUntil,extractText,renderWithLayout -
Analytics Testing: Always use
toMatchInlineSnapshot()pattern for tracking events -
Async Operations: Use
findBy*queries, notwaitUntilor promise flushing
Test Structure Pattern
Follow Arrange-Act-Assert:
describe("ComponentName", () => {
it("does something specific", () => {
// Arrange: Set up and render
renderWithWrappers(<Component />)
// Act: Trigger behavior
fireEvent.press(screen.getByTestId("button-id"))
// Assert: Verify outcome
expect(mockNavigate).toHaveBeenCalledWith("/path")
})
})
Common Patterns
Testing Navigation
import { navigate } from "app/system/navigation/navigate"
expect(navigate).toHaveBeenCalledWith("/artwork/artwork-slug")
Testing Analytics
import { mockTrackEvent } from "app/utils/tests/globallyMockedStuff"
expect(mockTrackEvent).toHaveBeenCalledTimes(1)
expect(mockTrackEvent.mock.calls[0]).toMatchInlineSnapshot()
// Run test to generate snapshot, then verify it's correct
Testing Relay Data
renderWithRelay({
Me: () => ({
name: "John Doe",
artworks: {
edges: mockEdges(10), // Use mockEdges for paginated data
},
}),
})
Testing Error States
const { mockRejectLastOperation } = renderWithRelay()
mockRejectLastOperation(new Error("Network error"))
Detailed Guidelines
For comprehensive testing patterns, utilities, and examples, refer to:
- references/testing-guidelines.md - Complete testing documentation
Read this file when you need:
- Detailed examples of testing patterns
- Information about wrapper props and configuration
- Guidance on what to test and what not to test
- Mock helpers and utilities
- Additional resources and links
TestID Conventions
Use descriptive, kebab-case test IDs:
-
artwork-save-button -
artist-series-list-item -
price-display-container
Running Tests
yarn test # Run all tests
yarn test:watch # Watch mode
yarn test path/to/file.tests.tsx # Test specific file
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-03-11
- 索引更新时间
- 2026-03-11
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!