You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: full-suite-stabilization.plan.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -251,6 +251,18 @@ Tracked failing tests from the current baseline:
251
251
- move the remaining SPA route-changing interactions onto the shared `ClickAndContinueAsync(..., noWaitAfter: true)` path
252
252
- harden reader timing and reverse-transition assertions against poll jitter while keeping the user-visible behavior contract intact
253
253
- route editor open/theme/split/title flows through the shared route helpers and interaction driver so local and CI follow the same readiness path
254
+
-[x]`Release Pipeline` run `24234983323` fails remotely in `Shell` and `Editor` after commit `ee5f0fb`
255
+
Symptom:
256
+
-`Shell` still times out in a small route-transition cluster where the UI remains on `library-page` after import/playback actions instead of completing the intended move into `editor`, `learn`, or `reader`
257
+
-`Editor` still flakes in local-history flows, with one test timing out after opening `/settings` and another timing out after a raw page reload while the editor is already visibly present
258
+
Root cause:
259
+
- several remaining SPA route-changing clicks were still using default Playwright navigation waiting instead of the shared no-wait click contract plus explicit route-ready waits, so CI could stall on scheduled client-side transitions
260
+
- some return-to-editor paths only waited for `editor-page` instead of full Monaco readiness
261
+
-`EditorLocalHistoryFlowTests` still bypassed the shared route helpers with raw `GotoAsync("/settings")` and raw `ReloadAsync()`, which made the tests diverge from the rest of the browser harness under slower remote startup
262
+
Fix path:
263
+
- move the remaining route-changing shell, reader, and studio clicks onto `UiInteractionDriver.ClickAndContinueAsync(..., noWaitAfter: true)` where the test already owns the post-click readiness contract
264
+
- upgrade learn/teleprompter/editor return waits to the shared ready helpers so route completion is measured by the real interactive surface, not just the shell frame
265
+
- route editor local-history settings/reload operations through `ShellRouteDriver.OpenSettingsAsync(...)` and `BrowserRouteDriver.ReloadPageAsync(...)` so local and CI share the same readiness path
254
266
255
267
## Ordered Plan
256
268
@@ -289,6 +301,7 @@ Tracked failing tests from the current baseline:
-`dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx --max-parallel-test-modules 1` passed with `1162/1162` green in `7m 42.943s`
291
303
- post-format verification repeated successfully with `dotnet build ./PrompterOne.slnx -warnaserror` and `dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx --max-parallel-test-modules 1`, ending at `1162/1162` green in `7m 35.996s`
304
+
- latest post-remediation verification repeated successfully with `dotnet format ./PrompterOne.slnx`, `dotnet build ./PrompterOne.slnx -warnaserror`, and `dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx --max-parallel-test-modules 1`, ending at `1162/1162` green in `7m 47.418s`
292
305
293
306
-[ ] Step 5. Publish directly to `main`.
294
307
Actions:
@@ -327,3 +340,9 @@ Tracked failing tests from the current baseline:
327
340
-`dotnet test @./tests/dotnet-test-progress.rsp --project ./tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj` passed with `168/168`
328
341
-`dotnet test @./tests/dotnet-test-progress.rsp --project ./tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj` passed with `38/38`
329
342
-`dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx --max-parallel-test-modules 1` passed with `1162/1162` green in `7m 44.199s`
343
+
-[x] Follow-up remediation for remote run `24234983323`
-`dotnet test @./tests/dotnet-test-progress.rsp --solution ./PrompterOne.slnx --max-parallel-test-modules 1` passed with `1162/1162` green in `7m 47.418s`
348
+
-`Shell`, `Reader`, `Studio`, and `Editor` all completed green inside that solution-level validation run
0 commit comments