ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Spec 206: implement test suite governance foundation #239

Merged
ahmido merged 1 commits from 206-test-suite-governance into dev 2026-04-16 13:58:51 +00:00
Conversation 0 Commits 1 Files Changed 55 +4281 -141
ahmido commented 2026-04-16 13:57:59 +00:00
Owner
Copy Link

Summary

This PR implements Spec 206 end to end and establishes the first checked-in test suite governance foundation for the platform app.

Key changes:

  • add manifest-backed test lanes for fast-feedback, confidence, browser, heavy-governance, profiling, and junit
  • add budget and report helpers plus app-local artifact generation under apps/platform/storage/logs/test-lanes
  • add repo-root Sail-friendly lane/report wrappers
  • switch the default contributor test path to the fast-feedback lane
  • introduce explicit fixture profiles and cheaper defaults for shared tenant/provider test setup
  • add minimal/heavy factory states for tenant and provider connection setup
  • migrate the first high-usage and provider-sensitive tests to explicit fixture profiles
  • document budgets, taxonomy rules, DB reset guidance, and the full Spec 206 plan/contracts/tasks set

Validation

Executed during implementation:

  • focused Spec 206 guard/support/factory validation pack: 31 passed
  • provider-sensitive regression pack: 29 passed
  • first high-usage caller migration pack: 120 passed
  • lane routing and wrapper validation succeeded
  • pint completed successfully

Measured lane baselines captured in docs:

  • fast-feedback: 176.74s
  • confidence: 394.38s
  • heavy-governance: 83.66s
  • browser: 128.87s
  • junit: 380.14s
  • profiling: 2701.51s
  • full-suite baseline anchor: 2624.60s

Notes

  • Livewire v4 / Filament v5 runtime behavior is unchanged by this PR.
  • No new runtime routes, product UI flows, or database migrations are introduced.
  • Panel provider registration remains unchanged in bootstrap/providers.php.
## Summary This PR implements Spec 206 end to end and establishes the first checked-in test suite governance foundation for the platform app. Key changes: - add manifest-backed test lanes for fast-feedback, confidence, browser, heavy-governance, profiling, and junit - add budget and report helpers plus app-local artifact generation under `apps/platform/storage/logs/test-lanes` - add repo-root Sail-friendly lane/report wrappers - switch the default contributor test path to the fast-feedback lane - introduce explicit fixture profiles and cheaper defaults for shared tenant/provider test setup - add minimal/heavy factory states for tenant and provider connection setup - migrate the first high-usage and provider-sensitive tests to explicit fixture profiles - document budgets, taxonomy rules, DB reset guidance, and the full Spec 206 plan/contracts/tasks set ## Validation Executed during implementation: - focused Spec 206 guard/support/factory validation pack: 31 passed - provider-sensitive regression pack: 29 passed - first high-usage caller migration pack: 120 passed - lane routing and wrapper validation succeeded - pint completed successfully Measured lane baselines captured in docs: - fast-feedback: 176.74s - confidence: 394.38s - heavy-governance: 83.66s - browser: 128.87s - junit: 380.14s - profiling: 2701.51s - full-suite baseline anchor: 2624.60s ## Notes - Livewire v4 / Filament v5 runtime behavior is unchanged by this PR. - No new runtime routes, product UI flows, or database migrations are introduced. - Panel provider registration remains unchanged in `bootstrap/providers.php`.
ahmido added 1 commit 2026-04-16 13:57:59 +00:00
ahmido merged commit 3c38192405 into dev 2026-04-16 13:58:51 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#239
No description provided.
Delete Branch "206-test-suite-governance"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?