Skip to content

docs: correct test count and the DB-update readiness step #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bilbospocketses merged 1 commit into from
Aug 26, 2026
Merged

docs: correct test count and the DB-update readiness step #121

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Open http://localhost:5159 in your browser. The first-run wizard will guide you
dotnet test
```

713 tests covering services, modules, the launcher, and integrations (across `ControlMenu.Tests`, `ControlMenu.Common.Tests`, and `ControlMenuLauncher.Tests`).
726 tests covering services, modules, the launcher, and integrations (across `ControlMenu.Tests`, `ControlMenu.Common.Tests`, and `ControlMenuLauncher.Tests`).

## Architecture

Expand Down
2 changes: 1 addition & 1 deletion docs/TECHNICAL_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1064,7 +1064,7 @@ All paths resolve under `<dataRoot>` via `IDataPathResolver` — `C:\ProgramData
- **xUnit** -- test runner
- **Moq** -- mocking framework
- **bunit** -- Blazor (Razor) component testing
- **713 tests** (all green on net10.0) across three projects — `ControlMenu.Tests` (app), `ControlMenu.Common.Tests`, and `ControlMenuLauncher.Tests` — run together via `ControlMenu.sln`
- **726 tests** (all green on net10.0) across three projects — `ControlMenu.Tests` (app), `ControlMenu.Common.Tests`, and `ControlMenuLauncher.Tests` — run together via `ControlMenu.sln`

### Test Database

Expand Down
4 changes: 2 additions & 2 deletions docs/manual-test-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,7 +275,7 @@ Post-audit verification. Run the app with `dotnet run` from `src/ControlMenu/`.
- [ ] Step 1: Container stops (shows truncated container ID)
- [ ] Step 2: Backup created
- [ ] Step 3: SQL update runs
- [ ] Step 4: Container starts, **waits for "Startup complete"** (should now actually detect it via stderr)
- [ ] Step 4: Container starts, then **waits for Jellyfin to be ready** — the container healthcheck reporting `healthy`, or `Startup complete` in logs timestamped *after* this start. Budget 120s. A failure here means "started but never reported ready", which is NOT `docker start` failing — the step text distinguishes the two
- [ ] Step 5: Old backups cleaned
- [ ] All steps show green checkmarks on success
- [ ] If any step fails: error shows immediately (red X), **container is restarted** on failure
Expand Down Expand Up @@ -397,7 +397,7 @@ If you're short on time, just hit these:
4. [ ] Settings > General: SMTP fields save without reverting
5. [ ] Settings > Cameras: save a camera, verify name shows in sidebar after refresh
6. [ ] Settings > Dependencies: badges are styled, disabled buttons are dimmed
7. [ ] Jellyfin > DB Date Update: start a run, verify Step 4 detects "Startup complete"
7. [ ] Jellyfin > DB Date Update: start a run, verify Step 4 reports Jellyfin online (healthcheck or post-start log marker), not a false "failed to start"
8. [ ] Edit a device, cancel — verify original values unchanged
9. [ ] Google TV mirror: clicks work, survive stream refresh
10. [ ] Cast & Crew update sends email on completion (if notification email set)
Expand Down