SluijsensandClaude Sonnet 5
0447993181
Frontend (Unit 2 completion): dual dev-server tooling (pnpm dev:slave, pnpm dev:all), per-instance browser tab titles, and a backend capability check (SystemController + useSystemCapabilities + ModuleGuard) so a Master-only page is hidden on a slave instance instead of assuming every backend has every module. Master/slave protocol fixes surfaced by actually running master and slave side by side locally: - Deactivating a CMS instance (Inactive) now releases the slave's master gate instead of leaving it stuck on its last pushed status. - The periodic integrity check now also re-pushes status to every reachable slave (previously URL-verification only) and runs once immediately on startup. - Added the originally-specified (but never implemented) slave-pull path: a slave now periodically polls its own status from the master (GET /api/v1/SlaveStatus) and fails open to Available if the master is unreachable for too long, complementing the existing push. - The slave's own Settings page can no longer "successfully" change local availability while the master controls it; it's now locked with an explanatory banner and the backend rejects the write with 409 instead of silently no-op'ing it. - CMS instance status badges now match the dashboard's color/icon styling instead of a plain grey badge. Also corrected the master-cms-module design docs to match this as-built behavior, and flagged (without a full rewrite) a larger, pre-existing divergence between its inception-stage application design and what construction actually built. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
# Unit Test Execution — Local Dev Master/Slave Setup
|
|
|
|
## Run Unit Tests
|
|
|
|
### 1. Execute All Unit Tests
|
|
```powershell
|
|
dotnet test SlpModularCms.sln
|
|
```
|
|
|
|
### 2. Review Test Results
|
|
- **Expected**: All existing test suites pass unchanged — this feature adds no new business logic, so no new unit tests were written (per Unit of Work Q3 = A).
|
|
- **Test Coverage**: Unchanged from before this feature (the relocated `ModuleOrchestrator`/`ApiPrefixConvention` classes retain their existing test coverage, now in `SlpModularCms.Core.Tests/Hosting/` instead of `SlpModularCms.Modules.Identity.Tests/Infrastructure/`).
|
|
- **Test Report Location**: Console output from `dotnet test`; no separate report file generated by default.
|
|
|
|
### Actual Result (this session)
|
|
Ran `dotnet test SlpModularCms.sln`:
|
|
|
|
| Test Project | Passed | Failed | Skipped |
|
|
|---|---|---|---|
|
|
| `SlpModularCms.Core.Tests` (incl. relocated `Hosting` tests) | 54 | 0 | 0 |
|
|
| `SlpModularCms.Modules.Availability.Tests` | 60 | 0 | 0 |
|
|
| `SlpModularCms.Modules.Identity.Tests` | 37 | 0 | 0 |
|
|
| `SlpModularCms.Modules.Master.Tests` | 42 | 0 | 0 |
|
|
| **Total** | **193** | **0** | **0** |
|
|
|
|
No regressions from relocating `ModuleOrchestrator`, `ServiceCollectionExtensions`, and `ApiPrefixConvention` into `SlpModularCms.Core`, or from moving their tests into `Core.Tests`.
|
|
|
|
### 3. Fix Failing Tests
|
|
Not applicable this run — all tests passed on first execution after Code Generation.
|