Standardize testID constants in React Native with hierarchical naming conventions.
npx skills add https://github.com/guicheffer/devorch-cli --skill test-ids
Please help me install this Agent Skill. Skill: test-ids Source: https://github.com/guicheffer/devorch-cli/tree/main/templates/skills/testing/test-ids Command: npx skills add https://github.com/guicheffer/devorch-cli --skill test-ids
This Skill addresses the challenge of creating reliable and maintainable automated tests for React Native applications by establishing a consistent pattern for defining and using testID attributes.
feature-component-element-variant naming convention to prevent collisions and improve discoverability.testIDs as constants within feature-specific files, enabling easier refactoring and preventing typos.testIDs in both unit tests (React Native Testing Library) and E2E tests (Maestro).testIDs like profile-screen-header, profile-screen-edit-button, and profile-screen-avatar ensuring consistency and testability.Define test IDs for your React Native components using the feature-component-element naming convention.
High-intent search queries and answers about installing and using this skill.
Standardize React Native testIDs by enforcing a hierarchical `feature-component-element-variant` naming convention. This pattern prevents identifier collisions and ensures reliable element location during automated testing across different components and features.
Preventing testID collisions requires a hierarchical naming convention like `feature-component-element-variant`. Defining these identifiers as constants within feature-specific files further eliminates typos and ensures unique element identification across the application.
Yes, the same React Native testIDs can be used for both unit and E2E tests. This cross-platform compatibility allows unified element identification across React Native Testing Library for unit tests and Maestro for E2E testing.
Structure testID constants by defining them within feature-specific files using the `feature-component-element` naming convention. For example, a user profile screen uses constants like `profile-screen-header` and `profile-screen-edit-button` to maintain testability.
Defining React Native testIDs as constants prevents typos and enables easier refactoring. Grouping these constants in feature-specific files ensures consistent usage across unit and E2E tests, maintaining reliable automated testing workflows.
bdfinstCreate React components with PropTypes, default props, and data-testid attributes.
amanhsnGenerate unit and end-to-end tests for React and Next.js applications.
guichefferStandardize data-testid attributes with kebab-case naming for web testing.
CodySwannGTDefine Playwright selector best practices for Expo web apps using testID and aria-label.