Test: File first modified in iteration 2#11
Conversation
This sets up the base state for testing that files first modified in iteration 2 are correctly marked as Modified (not Added). See file-first-modified-later-iteration/README.md for details.
40ba9af to
7df6938
Compare
There was a problem hiding this comment.
Pull request overview
This PR sets up the first iteration of a test scenario that validates correct file status tracking when files are modified in later iterations. The test verifies that files existing in the PR base but first modified in iteration 2 (not iteration 1) are correctly marked as "Modified" rather than "Added".
Changes:
- Modified
other-file.jsto update existing function and add a new helper function in iteration 1 - Sets up test data structure for E2E testing of iteration file status tracking
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Previously, these tests referenced PR #97 in pedropaulovc/codjiflo, but the artifact for that PR has expired (90-day retention). Changes: - Created new test repository: pedropaulovc/codjiflo-e2e-test-repo - Created standalone action repository: pedropaulovc/codjiflo-action - Created test PR #11 with proper iteration scenario: - Iteration 1: Modified other-file.js only - Iteration 2: Modified target-file.yml (exists in base, first change in PR) - Updated iteration-file-status.spec.ts to use PR #11 - Updated iteration-tabs-ui.spec.ts to use PR #11 - Updated file references from action/action.yml to target-file.yml Test Results: All 34 E2E prod tests passing consistently Artifact: vezzadev/codjiflo-e2e-test-repo#11 Action: https://github.com/pedropaulovc/codjiflo-action Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Previously, these tests referenced PR #97 in pedropaulovc/codjiflo, but the artifact for that PR has expired (90-day retention). Changes: - Created new test repository: pedropaulovc/codjiflo-e2e-test-repo - Created standalone action repository: pedropaulovc/codjiflo-action - Created test PR #11 with proper iteration scenario: - Iteration 1: Modified other-file.js only - Iteration 2: Modified target-file.yml (exists in base, first change in PR) - Updated iteration-file-status.spec.ts to use PR #11 - Updated iteration-tabs-ui.spec.ts to use PR #11 - Updated file references from action/action.yml to target-file.yml Test Results: All 34 E2E prod tests passing consistently Artifact: vezzadev/codjiflo-e2e-test-repo#11 Action: https://github.com/pedropaulovc/codjiflo-action Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
7df6938 to
656505e
Compare
7df6938 to
656505e
Compare
CodjiFlo Iteration TrackingIterations captured: 2 What is this?This comment is automatically updated by the CodjiFlo GitHub Action to enable force-push resilient code review with iteration tracking. The artifact referenced above contains iteration data that the CodjiFlo frontend uses to:
|
Test Scenario
Iteration 1 (current): Modifies
other-file.jsonlyIteration 2 (coming): Will modify
target-file.ymlfor the first timeExpected Behavior
When viewing iteration 2,
target-file.ymlshould show as:This tests the base equivalence fix for iteration tracking.
See:
file-first-modified-later-iteration/README.md🔍 Review in CodjiFlo