split tests

Author: KSemenenko

.github/workflows/deploy-github-pages.yml

@@ -20,7 +20,6 @@ env:
   CORE_TEST_PROJECT: tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj
   PLAYWRIGHT_CLI: tests/PrompterOne.Web.UITests/bin/Debug/net10.0/.playwright/package/cli.js
   SOLUTION_FILE: PrompterOne.slnx
-  UI_TEST_PROJECT: tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj
 
 jobs:
   build_supporting_suites:
@@ -74,8 +73,8 @@ jobs:
           dotnet test --project "$CORE_TEST_PROJECT"
           dotnet test --project "$APP_TEST_PROJECT"
 
-  build_browser_suite:
-    name: Restore + Build Browser Suite
+  build_browser_suites:
+    name: Restore + Build Browser Suites
     runs-on: macos-latest
 
     permissions:
@@ -96,10 +95,26 @@ jobs:
       - name: Build solution
         run: dotnet build "$SOLUTION_FILE" -warnaserror
 
-  test_browser_suite:
-    name: Run Browser Suite
-    needs: build_browser_suite
+  test_browser_suites:
+    name: Run Browser Suite (${{ matrix.suite.name }})
+    needs: build_browser_suites
     runs-on: macos-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        suite:
+          - name: Shell
+            artifact: shell
+            project: tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj
+          - name: Studio
+            artifact: studio
+            project: tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj
+          - name: Editor
+            artifact: editor
+            project: tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj
+          - name: Reader
+            artifact: reader
+            project: tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj
 
     permissions:
       contents: read
@@ -130,20 +145,20 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        run: dotnet test --project "$UI_TEST_PROJECT"
+        run: dotnet test --project "${{ matrix.suite.project }}"
 
       - name: Upload Playwright artifacts
         if: always()
         uses: actions/upload-artifact@v7
         with:
-          name: playwright-artifacts-release-pipeline
+          name: playwright-artifacts-release-pipeline-${{ matrix.suite.artifact }}
           path: output/playwright/
           if-no-files-found: ignore
   prepare_release:
     name: Resolve Release Version
     needs:
       - test_supporting_suites
-      - test_browser_suite
+      - test_browser_suites
     runs-on: ubuntu-latest
     env:
       APP_PROJECT: src/PrompterOne.Web/PrompterOne.Web.csproj

.github/workflows/pr-validation.yml

@@ -18,7 +18,6 @@ env:
   CORE_TEST_PROJECT: tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj
   PLAYWRIGHT_CLI: tests/PrompterOne.Web.UITests/bin/Debug/net10.0/.playwright/package/cli.js
   SOLUTION_FILE: PrompterOne.slnx
-  UI_TEST_PROJECT: tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj
 
 jobs:
   build_supporting_suites:
@@ -66,8 +65,8 @@ jobs:
           dotnet test --project "$CORE_TEST_PROJECT"
           dotnet test --project "$APP_TEST_PROJECT"
 
-  build_browser_suite:
-    name: Restore + Build Browser Suite
+  build_browser_suites:
+    name: Restore + Build Browser Suites
     runs-on: macos-latest
 
     steps:
@@ -85,10 +84,26 @@ jobs:
       - name: Build solution
         run: dotnet build "$SOLUTION_FILE" -warnaserror
 
-  test_browser_suite:
-    name: Run Browser Suite
-    needs: build_browser_suite
+  test_browser_suites:
+    name: Run Browser Suite (${{ matrix.suite.name }})
+    needs: build_browser_suites
     runs-on: macos-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        suite:
+          - name: Shell
+            artifact: shell
+            project: tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj
+          - name: Studio
+            artifact: studio
+            project: tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj
+          - name: Editor
+            artifact: editor
+            project: tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj
+          - name: Reader
+            artifact: reader
+            project: tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj
 
     steps:
       - name: Checkout
@@ -116,12 +131,12 @@ jobs:
         run: node "$PLAYWRIGHT_CLI" install chromium
 
       - name: Test browser suite
-        run: dotnet test --project "$UI_TEST_PROJECT" --verbosity normal
+        run: dotnet test --project "${{ matrix.suite.project }}" --verbosity normal
 
       - name: Upload Playwright artifacts
         if: always()
         uses: actions/upload-artifact@v7
         with:
-          name: playwright-artifacts-pr-validation
+          name: playwright-artifacts-pr-validation-${{ matrix.suite.artifact }}
           path: output/playwright/
           if-no-files-found: ignore

AGENTS.md

@@ -110,6 +110,7 @@ Rule format:
 - For deploy-only, domain, CI, or static-site hosting tasks, do not spend time on unrelated app/browser test suites unless the user explicitly asks or the runtime behavior itself changes; prefer workflow, build, and publish-config validation only.
 - Repo-wide .NET SDK and test-runner selection belong in the root `global.json`; do not split `global.json` test-runner opt-ins per project or subfolder once the user asks for a global test-platform policy.
 - Browser and component tests must use one selector format only: `data-test`; do not mix in any alternate test-attribute naming variants.
+- Every runnable test project must declare `MaxParallelTestsForPipeline : EnvironmentAwareParallelLimitBase` with `LocalLimit = 15`; do not keep lower per-project local parallel caps unless the user explicitly asks for an exception.
 - Selector-contract remediation requests must be handled repo-wide across all relevant test files (`Web.Tests` and `Web.UITests`), not as partial per-file cleanups.
 - Repo-wide quality audits and agent-generated review handoff artifacts must be written as root-level task files so other coding agents can pick them up quickly; do not bury those temporary audit results under `docs/` unless the task is explicitly about durable product documentation.
 - Repo-wide cleanup and review passes must explicitly inventory forbidden implementation string literals, `MarkupString` or raw-HTML UI composition, duplicated JS/CSS patterns, architecture-boundary drift, and `foreach`-driven test scenarios that should become isolated TUnit cases.
@@ -122,9 +123,9 @@ Rule format:
 ### Commands
 
 - `build`: `dotnet build ./PrompterOne.slnx -warnaserror`
-- `test`: `dotnet test --project ./tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj && dotnet test --project ./tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj`
+- `test`: `dotnet test --project ./tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj && dotnet test --project ./tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj`
 - `format`: `dotnet format ./PrompterOne.slnx`
-- `coverage`: `dotnet test --project ./tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj -- --coverage --coverage-output-format cobertura`
+- `coverage`: `dotnet test --project ./tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj -- --coverage --coverage-output-format cobertura && dotnet test --project ./tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj -- --coverage --coverage-output-format cobertura`
 
 For this `.NET` repo:
 
@@ -139,18 +140,22 @@ Useful focused commands:
 - app run: `cd ./src/PrompterOne.Web && dotnet run`
 - core tests: `dotnet test --project ./tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj`
 - component tests: `dotnet test --project ./tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj`
-- ui tests: `dotnet test --project ./tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj`
+- ui tests: `dotnet test --project ./tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj && dotnet test --project ./tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj`
+- ui shell tests: `dotnet test --project ./tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj`
+- ui studio tests: `dotnet test --project ./tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj`
+- ui editor tests: `dotnet test --project ./tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj`
+- ui reader tests: `dotnet test --project ./tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj`
 - playwright browser install: `node ./tests/PrompterOne.Web.UITests/bin/Debug/net10.0/.playwright/package/cli.js install chromium`
 - Build the relevant project immediately before starting a local dev server so `dotnet run` cannot serve stale WASM assets or binaries.
 
 Browser test execution rules:
 
-- Use one `dotnet test` process at a time for the browser suite.
-- The browser suite self-hosts the built WASM assets on a dynamically assigned loopback HTTP origin.
+- Use one `dotnet test` process at a time for a browser suite project when running locally.
+- The browser suite family self-hosts the built WASM assets on a dynamically assigned loopback HTTP origin.
 - Each browser-suite host startup MUST request a fresh OS-assigned loopback port via `http://127.0.0.1:0`. Never pin or reuse a fixed browser-test port across runs.
-- Inside that single process, the browser suite may run up to `4` parallel TUnit workers locally; when repeated full-suite CI runs prove resource contention, lower the CI worker cap instead of weakening browser assertions.
-- Do not run `PrompterOne.Web.UITests` in parallel with another `dotnet build` or `dotnet test` command.
-- In GitHub Actions, run the browser suite in its own dedicated macOS job and keep supporting suites in a separate job so CI can parallelize work without Linux x64 browser-runner contention stretching release validation.
+- Inside a single browser-suite process, the suite may run up to `15` parallel TUnit workers locally; when repeated full-suite CI runs prove resource contention, lower the CI worker cap instead of weakening browser assertions.
+- Do not run any `PrompterOne.Web.UITests*` project in parallel with another `dotnet build` or `dotnet test` command on the same local machine context.
+- In GitHub Actions, run the browser suite family in dedicated macOS jobs or matrix entries and keep supporting suites in separate jobs so CI can parallelize work without Linux x64 browser-runner contention stretching release validation.
 - GitHub Actions pipelines must expose explicit staged jobs with readable names such as restore, build, supporting tests, browser tests, release publish, and deploy; vague single-job `validate` graphs are not acceptable when the user needs to see pipeline phases clearly in the Actions UI.
 - When monitoring long-running GitHub Actions jobs from the terminal, poll with coarse waits of roughly `3-5` minutes between checks; frequent short-interval polling is noise and does not help on multi-minute browser suites.
 - Browser acceptance tests must stay on the production-shaped runtime path; do not add or keep `?wasm-debug=1` or similar debug-query scenarios in automated acceptance coverage unless the user explicitly asks for that path.
@@ -200,6 +205,10 @@ Current local `AGENTS.md` files:
 - [tests/PrompterOne.Testing/AGENTS.md](./tests/PrompterOne.Testing/AGENTS.md)
 - [tests/PrompterOne.Web.Tests/AGENTS.md](./tests/PrompterOne.Web.Tests/AGENTS.md)
 - [tests/PrompterOne.Web.UITests/AGENTS.md](./tests/PrompterOne.Web.UITests/AGENTS.md)
+- [tests/PrompterOne.Web.UITests.Shell/AGENTS.md](./tests/PrompterOne.Web.UITests.Shell/AGENTS.md)
+- [tests/PrompterOne.Web.UITests.Studio/AGENTS.md](./tests/PrompterOne.Web.UITests.Studio/AGENTS.md)
+- [tests/PrompterOne.Web.UITests.Editor/AGENTS.md](./tests/PrompterOne.Web.UITests.Editor/AGENTS.md)
+- [tests/PrompterOne.Web.UITests.Reader/AGENTS.md](./tests/PrompterOne.Web.UITests.Reader/AGENTS.md)
 
 ### Maintainability Limits
 

PrompterOne.slnx

@@ -9,6 +9,10 @@
     <Project Path="tests/PrompterOne.Testing/PrompterOne.Testing.csproj" />
     <Project Path="tests/PrompterOne.Web.Tests/PrompterOne.Web.Tests.csproj" />
     <Project Path="tests/PrompterOne.Web.UITests/PrompterOne.Web.UITests.csproj" />
+    <Project Path="tests/PrompterOne.Web.UITests.Shell/PrompterOne.Web.UITests.Shell.csproj" />
+    <Project Path="tests/PrompterOne.Web.UITests.Studio/PrompterOne.Web.UITests.Studio.csproj" />
+    <Project Path="tests/PrompterOne.Web.UITests.Editor/PrompterOne.Web.UITests.Editor.csproj" />
+    <Project Path="tests/PrompterOne.Web.UITests.Reader/PrompterOne.Web.UITests.Reader.csproj" />
     <Project Path="tests/PrompterOne.Core.Tests/PrompterOne.Core.Tests.csproj" />
   </Folder>
 </Solution>