# 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.