docs: add comprehensive testing strategy#137
Merged
Merged
Conversation
Add detailed testing strategy document covering: - Testing goals and TDD principles - Testing pyramid with 80%+ coverage target - Unit, component, integration, and E2E testing strategies - Tool setup (Vitest, React Testing Library, Playwright) - Mocking strategies and best practices - CI/CD integration guidelines - Implementation roadmap with 7 phases Target: 80%+ overall coverage, 100% for critical paths Priority: Component tests (React Testing Library) and key E2E workflows Scope: Chrome only, no cross-browser automated testing
Rewrite testing.md to focus on strategy rather than implementation: - Remove all code examples and specific function references - Remove general TDD explanations (keep project-specific only) - Remove ASCII art diagrams - Condense from 2000+ to ~350 lines - Focus on: goals, approach, coverage targets, tools, roadmap Document now clearly defines WHAT to test, WHY, and HOW at strategic level.
Add references to docs/testing.md in four locations: - Testing Strategy section: Add prominent reference and simplify content - Documentation section: Add testing.md to file list - Resources section: Add Testing Strategy to project documentation - For AI Agents section: Add testing.md to important resources All references point to comprehensive testing strategy document.
…ture Add cross-references to testing.md in: - development-guideline.md: Testing Guidelines section - architecture.md: テスト戦略と依存関係 section Makes testing strategy more discoverable when reading development docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add detailed testing strategy document covering:
Target: 80%+ overall coverage, 100% for critical paths
Priority: Component tests (React Testing Library) and key E2E workflows
Scope: Chrome only, no cross-browser automated testing