Add full e2e test: define -> implement -> execute workflow#45
Merged
Conversation
Replace Markdown with JSON array - CLA Assistant action expects JSON format for storing signatures. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
CLA Assistant expects { "signedContributors": [] } format,
not a plain array.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Per CLA Assistant docs: "You do not need to create this file manually. Our workflow will create the signature file if it does not already exist. Manually creating this file will cause the workflow to fail." Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add a deterministic 'fruits' test job and comprehensive CI tests to validate that deepwork-generated commands work correctly with Claude Code. Changes: - Add fruits job fixture (identify + classify steps) for CI testing - Add integration tests for fruits workflow (8 tests) - Add e2e tests for Claude Code execution (3 tests, skipped without API key) - Add GitHub Actions workflow for automated testing: - validate-generation: Always runs, tests command generation - claude-code-e2e: Runs with ANTHROPIC_API_KEY, tests actual execution The fruits job is designed to be deterministic: - Input: comma-separated list of items (e.g., "apple, car, banana") - Step 1: Identify which items are fruits - Step 2: Classify fruits by category (citrus, tropical, etc.)
- Add concurrency rules to ensure only one instance runs per PR - Fix test to use 'deepwork install --platform claude --path test_project' - Create .claude directory before install for platform detection - Run commands from repo root with --path flag instead of cd'ing
Update the claude-code-e2e job to test the COMPLETE DeepWork workflow: 1. /deepwork_jobs.define - Create a new job from scratch 2. /deepwork_jobs.implement - Generate step instruction files 3. /fruits.identify - Execute the generated identify command 4. /fruits.classify - Execute the generated classify command This tests the actual user experience rather than just validating pre-existing fixtures. The test provides deterministic instructions for creating a 'fruits' job with identify and classify steps.
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.
Summary
Updates the Claude Code e2e test to verify the complete DeepWork workflow:
/deepwork_jobs.define- Create a new job from scratch (fruits job)/deepwork_jobs.implement- Generate step instruction files/fruits.identify- Execute the generated identify command/fruits.classify- Execute the generated classify commandThis tests the actual user experience rather than just validating pre-existing fixtures.
Changes
Test plan
workflow_dispatchto test the full e2e flow🤖 Generated with Claude Code