axe some redundancy

This commit is contained in:
sepeterson
2026-07-16 10:22:31 -05:00
parent a291a35ccc
commit 21cdf0e465
4 changed files with 3 additions and 17 deletions

5
.gitignore vendored
View File

@@ -118,9 +118,6 @@ artifacts/
# Rubocop cache
**/tmp/rubocop_cache
# Claude Code local config, specialty agents, commands, hooks, and skills.
# Shared AI-agent guidance lives in AGENTS.md, .claude/CLAUDE.md, and agent-docs/.
# Ignore .claude/ contents but keep the tracked CLAUDE.md wrapper. A parent dir
# excluded with `.claude/` can't have children re-included, so ignore per-entry.
# Claude Code local config except CLAUDE.md
.claude/*
!.claude/CLAUDE.md

View File

@@ -309,7 +309,7 @@ In-depth architecture and convention docs for both humans and AI agents. Read th
- `architecture/``upload-system.md`, `navigation-patterns.md`, `api-layer.md`, `realm-and-zustand.md` (includes working with Realm objects in the React layer)
- `conventions/``component-conventions.md`, `i18n-conventions.md`, `import-aliases.md`, `typescript.md`
- `testing/``test-core.md`, `test-components.md`, `test-integrations.md`, `integration-test-analysis.md`, `e2e.md` (Detox + Maestro + iOS verification)
- `testing/``test-core.md`, `test-components.md`, `integration-test-analysis.md`, `e2e.md` (Detox + Maestro + iOS verification)
## Common Pitfalls

View File

@@ -75,4 +75,4 @@ Hard-won gotchas when driving the live app (e.g. via the Maestro MCP tools) rath
## Related
- Unit / component / integration testing: `test-core.md`, `test-components.md`, `test-integrations.md`, `integration-test-analysis.md` in this directory.
- Unit / component / integration testing: `test-core.md`, `test-components.md`, `integration-test-analysis.md` in this directory.

View File

@@ -1,11 +0,0 @@
# Purpose: Test how components integrate with real systems like Realm database, API calls, and navigation.
In the project directory, these tests are under /tests/integration/
For a comprehensive analysis of patterns, quality assessment, and strategic recommendations, see [integration-test-analysis.md](./integration-test-analysis.md).
## Strategy:
- Real database: Use actual Realm instances (via setupUniqueRealm) and write real data
- Real navigation: Render components within the full navigation stack using renderAppWithComponent
- API mocking: Mock API responses (like inatjs.observations.fetch) but test the full data flow
- Cross-system testing: Verify data persistence, sync operations, and multi-component interactions