fix: improve E2E test orchestration to prevent Red-phase blocking #69
Conversation
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
- Limit Phase 0 to unit tests only, excluding E2E/integration tests - E2E tests now run when implementation is complete for behavior verification - Add explicit test type classification (unit/E2E/integration) - Update orchestrator to pass test type info to work-planner - Clarify that E2E tests don't follow Red-Green-Refactor process This prevents E2E tests from getting stuck in Red phase due to missing implementation, ensuring proper quality checks at appropriate timing. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Sync English documentation with Japanese E2E test handling changes - Clarify that Phase 0 is for unit tests only, not E2E/integration tests - Specify E2E tests run when implementation is complete for behavior verification - Add test type classification (unit/E2E/integration) in work-planner - Update orchestrator communication to include test type information - Ensure AI execution accuracy with clear, unambiguous English instructions This maintains consistency across all language versions and ensures proper E2E test execution timing regardless of documentation language. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
shinpr
force-pushed
the
fix/e2e-test-orchestration
branch
2 times, most recently
from
3c60553 to
048709e
Compare
…and E2E tests - Rename e2e-test-generator to acceptance-test-generator for broader test coverage - Separate integration tests (run with implementation) from E2E tests (run at final phase) - Clarify that E2E tests skip Red-Green-Refactor cycle due to their nature - Change terminology from "E2E confirmation steps" to "operational confirmation steps" - Update test execution timing: integration tests during each phase, E2E tests only at completion This change improves test strategy clarity by distinguishing immediate integration testing from final E2E validation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
shinpr
force-pushed
the
fix/e2e-test-orchestration
branch
from
e898b35 to
0babd7c
Compare
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
shinpr
force-pushed
the
fix/e2e-test-orchestration
branch
from
d4bafcc to
552d587
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This prevents E2E tests from getting stuck in Red phase due to missing
implementation, ensuring proper quality checks at appropriate timing.