What problem does it solve? Choosing the right test type, environment, and conventions across Fedi's three UI workspaces (common, native, web) is error-prone; this Skill routes you to the correct patterns, mock builders, and run scripts so tests match existing suites. ## Core Features & Use Cases - Test-type decision guide: Routes work to unit, integration, or Appium e2e tests based on whether the change touches hooks, utilities, bridge RPCs, or navigation flows. - Environment-specific pattern references: Dedicated guides for ui/common, ui/native, and ui/web covering render helpers, provider-heavy vs providerless tests, and canonical example files. - Mock builder catalog: Documents createMockFedimintBridge, transaction/federation/Matrix event factories, and integration test builders like withFederationJoined and withEcashReceived. - Use Case: When adding a hook to ui/common that calls the real bridge, the Skill directs you to integration patterns, the IntegrationTestBuilder state helpers, and the correct run script (./scripts/ui/run-integration-tests.sh). ## Quick Start Ask the assistant to write a unit test for a specific hook or component in ui/native, ui/web, or ui/common and it will select the right patterns and mocks.
