WingtipToys Migration Test

End-to-end migration benchmark for the canonical WingtipToys Web Forms sample. This workflow uses the repository's migration toolkit as the public entry point, preserves the migrated application shape in samples\AfterWingtipToys\, and considers the run successful only when the existing Playwright acceptance tests pass.

Benchmark Integrity Rules

This workflow is a benchmark, so every run must start from scratch.

Required behavior

1. Start with the raw Web Forms source in samples\WingtipToys\.
2. Clear samples\AfterWingtipToys\ before each run.
3. Run migration-toolkit\scripts\bwfc-migrate.ps1 to produce the output for this run.
4. Repair only the fresh output produced during the current run.

Forbidden behavior

1. Do not restore or copy previously migrated content into samples\AfterWingtipToys\.
2. Do not use git history as migration input or repair content:
   • no git restore
   • no git checkout
   • no git show to pull old file contents into the run
   • no copying files from prior commits, branches, tags, or stashes
3. Do not reuse prior benchmark outputs from:
   • samples\AfterWingtipToys\
   • dev-docs\migration-tests\wingtiptoys\run*
   • session artifacts, temp folders, or prior migration snapshots
4. Do not treat an earlier repaired sample as the answer. The point of the run is to measure what the toolkit plus current repair work can achieve from scratch.

If a run uses prior migrated content or git-sourced repairs, the benchmark is invalid and must be restarted from a freshly cleared output folder.

Paths

Success Criteria

A Wingtip run is only a success when all of the following are true:

1. samples\AfterWingtipToys\ was cleared before the run.
2. The migration was started through migration-toolkit\scripts\bwfc-migrate.ps1.
3. The generated app was repaired in place until it builds and runs.
4. dotnet test src\WingtipToys.AcceptanceTests\ passes against the migrated app.
5. A new numbered report folder was written under dev-docs\migration-tests\wingtiptoys\runNN\.
6. The report includes total runtime, what worked well, what did not work well, and embedded screenshots proving the app is working.

Prerequisites

• .NET 10 SDK
• Playwright browsers installed for src\WingtipToys.AcceptanceTests\
• Local HTTPS dev certificate trusted if the run uses the default https://localhost:5001
• Any seed data or local DB setup required by the current samples\AfterWingtipToys implementation

If Playwright browsers have not been installed yet for this machine:

dotnet build src\WingtipToys.AcceptanceTests\WingtipToys.AcceptanceTests.csproj
pwsh src\WingtipToys.AcceptanceTests\bin\Debug\net10.0\playwright.ps1 install

Workflow

Phase 0: Preparation

1. Determine the next run number
   Scan dev-docs\migration-tests\wingtiptoys\run* folders and use the next numeric value after the current maximum. Preserve zero padding: run26, run27, etc.

2. Record the start timestamp
   Start total wall-clock timing before clearing the output folder.

3. Clear the output folder contents
   Delete everything under samples\AfterWingtipToys\ while keeping the folder itself.

4. Create the report folder early
   Create dev-docs\migration-tests\wingtiptoys\runNN\ and an images\ subfolder so logs and screenshots have a known destination from the start.

Phase 1: Layer 1 - Migration Toolkit Run

Run the toolkit wrapper, not the CLI directly:

pwsh -File migration-toolkit\scripts\bwfc-migrate.ps1 `
  -Path samples\WingtipToys `
  -Output samples\AfterWingtipToys `
  -Verbose

Record:

• Layer 1 duration
• Any CLI/toolkit summary output
• Whether the toolkit resolved the nested samples\WingtipToys\WingtipToys\ app root automatically
• Whether .razor output, scaffold files, and static assets were produced in the expected places

Phase 2: Layer 2/3 - Skill-Guided Repair

Load and apply the migration toolkit from migration-toolkit\:

• Read migration-toolkit/README.md for the overall approach and key principles
• Read migration-toolkit/skills/ — the toolkit contains all the skills needed for the repair phase; apply whichever skills are relevant to the errors and patterns encountered in the generated output

Repair the generated app in place. Do not replace it with a simplified rewrite or a fresh unrelated sample.

Important benchmark constraint:

• Every repair must be derived from the current run's freshly generated output, the raw Web Forms source, BWFC/toolkit rules, and normal debugging/build feedback.
• Do not import repaired files from previous runs, from git history, or from other saved artifacts.

Focus on:

• Keeping the generated project shape in samples\AfterWingtipToys\
• Preserving Web Forms semantics through BWFC shims where available
• NEVER replace generated BWFC data controls (ListView, FormView, GridView, DataList, Repeater) with manual HTML. Fix the generated markup to work with the BWFC component instead.
• Fixing build errors iteratively until the app runs cleanly enough for acceptance validation
• Treating the migration toolkit as the thing under test; manual fixes should be documented as toolkit gaps

Phase 3: Build Validation

Run:

dotnet build samples\AfterWingtipToys\WingtipToys.csproj

Record:

• Final build status
• Error and warning counts
• Major error categories encountered before the final green build

Phase 4: Run the Migrated App

Start the migrated app and wait until it is responsive.

Recommended default:

dotnet run --project samples\AfterWingtipToys\WingtipToys.csproj

Use the app's configured launch settings when possible. If you must override the base URL, keep it consistent with the acceptance tests and report it explicitly.

Phase 5: Acceptance Tests

Run the existing Playwright suite against the migrated app:

$env:WINGTIPTOYS_BASE_URL = "https://localhost:5001"
dotnet test src\WingtipToys.AcceptanceTests\WingtipToys.AcceptanceTests.csproj --verbosity normal

Record:

• Total / passed / failed / skipped counts
• Any test retries or targeted fixes needed
• Final pass condition

If the suite does not pass, the run is not successful. Continue repair work or write a failed run report that clearly explains the blocker.

Phase 6: Screenshot Capture

Capture proof screenshots from the working migrated app and save them under runNN\images\.

Recommended minimum set:

1. 01-home.png
2. 02-products.png
3. 03-product-details.png
4. 04-shopping-cart.png
5. 05-login.png
6. 06-about.png

Use additional screenshots when they clarify a major success or known defect.

Phase 7: Report Generation

Create dev-docs\migration-tests\wingtiptoys\runNN\report.md from REPORT-TEMPLATE.md.

The report must include:

• Run metadata (date, branch, operator if known)
• Source/output/tool paths
• Total wall-clock runtime
• Per-phase timing when available
• Final build result
• Final acceptance-test result
• What worked well
• What did not work well
• Toolkit/CLI gaps exposed by the run
• Embedded screenshot gallery using relative image paths

Optional supporting artifacts:

• summary.md
• raw-data.md
• captured command output snippets

Critical Rules

Suggested Output Structure

dev-docs/
  migration-tests/
    wingtiptoys/
      runNN/
        report.md
        summary.md                # optional
        raw-data.md               # optional
        images/
          01-home.png
          02-products.png
          03-product-details.png
          04-shopping-cart.png
          05-login.png
          06-about.png

Reference Documents

• migration-toolkit/ — the full toolkit (README, METHODOLOGY, skills, scripts)
• src/WingtipToys.AcceptanceTests/TestConfiguration.cs
• dev-docs/migration-tests/wingtiptoys/run25/report.md