Owner request (2026-11-16): "Dato che siamo su Windows prova ad avviare l'applicazione da qui e esegui test in autonomia."
CI has no Windows runner, so v1.1.0 shipped without these checks. They ran on the owner's Windows PC:
Release build, no warnings
Chronos.Core.Windows.Tests: 96/96
Chronos.App.Tests, including the classes that used to hang on this PC: 974 passed, 1 skipped. Five stale tests were fixed.
Screenshot capture and diff against the baselines: all 187 within tolerance after the updated baselines.
.gitea/scripts/installer-test.ps1 (install, upgrade, add/remove a program, legacy Uploader and Server 1.0). Not run. This PC has Chronos 1.0 installed for all users, so the script would ask UAC to upgrade the owner's install (DECISIONS 2026-11-16). It belongs on a clean Windows PC or VM.
The packed setup by hand: choose the programs, install, run. Partly done. The setup starts unelevated, but screen access to it was not granted. It was closed without installing.
The desktop app by hand, as a portable copy:
Settings › Server › Share this library;
closing the window keeps it in the tray;
Exit with clients connected asks first;
a client connecting (a token client on localhost; no second PC on the LAN).
Fixes found go into milestone v1.1.1: PR #71, released as v1.1.1. The user data in %LOCALAPPDATA%\Chronos was backed up to B:\chronos-tmp-wintest\localappdata-backup and never touched.
Owner request (2026-11-16): "Dato che siamo su Windows prova ad avviare l'applicazione da qui e esegui test in autonomia."
CI has no Windows runner, so v1.1.0 shipped without these checks. They ran on the owner's Windows PC:
- [x] Release build, no warnings
- [x] `Chronos.Core.Windows.Tests`: 96/96
- [x] `Chronos.App.Tests`, including the classes that used to hang on this PC: 974 passed, 1 skipped. Five stale tests were fixed.
- [x] Screenshot capture and diff against the baselines: all 187 within tolerance after the updated baselines.
- [ ] `.gitea/scripts/installer-test.ps1` (install, upgrade, add/remove a program, legacy Uploader and Server 1.0). **Not run.** This PC has Chronos 1.0 installed for all users, so the script would ask UAC to upgrade the owner's install (DECISIONS 2026-11-16). It belongs on a clean Windows PC or VM.
- [ ] The packed setup by hand: choose the programs, install, run. **Partly done.** The setup starts unelevated, but screen access to it was not granted. It was closed without installing.
- [x] The desktop app by hand, as a portable copy:
- Settings › Server › Share this library;
- closing the window keeps it in the tray;
- Exit with clients connected asks first;
- a client connecting (a token client on localhost; no second PC on the LAN).
Fixes found go into milestone v1.1.1: PR #71, released as `v1.1.1`. The user data in `%LOCALAPPDATA%\Chronos` was backed up to `B:\chronos-tmp-wintest\localappdata-backup` and never touched.
Alby96
added this to the v1.1.1 milestone 2026-11-16 12:11:24 +01:00
Chronos.App.Tests: 5 stale screen smoke tests fixed, now 969 passed and 1 skipped. Fixes:
Forget in Settings › Server › Certificates ran 5 px past the page in Bulgarian;
the Reorganize capture showed every sequence as unreadable.
Screenshots: 187 compared, only the two Reorganize baselines changed.
The portable 1.1.0 copy starts, creates its index (schema 11), and exits when its window closes with sharing off.
Blocked:
installer-test.ps1: this PC has Chronos 1.0.0 and Uploader 1.0.0 installed for all users (Program Files). With no per-user entry, the setup finds that install and asks UAC to upgrade or remove it. Run it on a clean Windows. The real 1.0 → 1.1 upgrade on this PC needs the owner's UAC approval.
Hands-on GUI test (import with "photo x of y", Reorganize on a real archive, sharing, tray, Exit with clients): screen control of the portable copy was not granted.
Progress (2026-11-16), PR #71:
Done:
- [x] Release build: 0 warnings.
- [x] `Chronos.Core.Windows.Tests`: 96 passed.
- [x] `Chronos.App.Tests`: 5 stale screen smoke tests fixed, now 969 passed and 1 skipped. Fixes:
- Forget in Settings › Server › Certificates ran 5 px past the page in Bulgarian;
- the Reorganize capture showed every sequence as unreadable.
- [x] Screenshots: 187 compared, only the two Reorganize baselines changed.
- [x] The portable 1.1.0 copy starts, creates its index (schema 11), and exits when its window closes with sharing off.
Blocked:
- [ ] `installer-test.ps1`: this PC has Chronos 1.0.0 and Uploader 1.0.0 installed for all users (Program Files). With no per-user entry, the setup finds that install and asks UAC to upgrade or remove it. Run it on a clean Windows. The real 1.0 → 1.1 upgrade on this PC needs the owner's UAC approval.
- [ ] Hands-on GUI test (import with "photo x of y", Reorganize on a real archive, sharing, tray, Exit with clients): screen control of the portable copy was not granted.
Hands-on GUI test of the portable 1.1.0 on the dev PC (2026-11-16):
Welcome and new archive: ok.
Folder import: 160 synthetic photos from two folders, two cameras, show "photo x of y" while copying and "sequence x of y" during quick analysis. The job log and the Library are correct.
Reorganize (dry run, then apply): the folders on disk are renamed.
Share this library:
in-process server on HTTPS 8443 / HTTP 8080;
/health ok, /admin/ 200;
Server › This library shows the addresses, ports, fingerprint and admin password.
Clients: a token client signed in with the generated admin password. It shows as "1 client · admin · Test client · ::1".
Tray:
closing the window hides it and keeps sharing (health 200);
Setup: the packed Chronos-Setup-1.1.0.exe starts unelevated. Its pages were not inspected (screen access not granted), and it was closed without installing.
Findings fixed in this branch:
F1: the job log showed UTC times while the rows show local time. The log now shows local time; the stored log stays UTC.
F2: the Type column cut "Analisi approfondita". It is now Auto, shared across rows, 90–170 px, in Jobs and Server › Jobs.
Hands-on GUI test of the portable 1.1.0 on the dev PC (2026-11-16):
- Welcome and new archive: ok.
- Folder import: 160 synthetic photos from two folders, two cameras, show "photo x of y" while copying and "sequence x of y" during quick analysis. The job log and the Library are correct.
- Reorganize (dry run, then apply): the folders on disk are renamed.
- Share this library:
- in-process server on HTTPS 8443 / HTTP 8080;
- `/health` ok, `/admin/` 200;
- Server › This library shows the addresses, ports, fingerprint and admin password.
- Clients: a token client signed in with the generated admin password. It shows as "1 client · admin · Test client · ::1".
- Tray:
- closing the window hides it and keeps sharing (health 200);
- the tray menu offers Open / Exit;
- Exit with an active client asks "Stop sharing?";
- Keep sharing keeps the server up;
- Exit stops sharing and ends Chronos (`share: Sharing stopped`, `app: Chronos exiting`).
- Setup: the packed `Chronos-Setup-1.1.0.exe` starts unelevated. Its pages were not inspected (screen access not granted), and it was closed without installing.
Findings fixed in this branch:
- F1: the job log showed UTC times while the rows show local time. The log now shows local time; the stored log stays UTC.
- F2: the Type column cut "Analisi approfondita". It is now Auto, shared across rows, 90–170 px, in Jobs and Server › Jobs.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner request (2026-11-16): "Dato che siamo su Windows prova ad avviare l'applicazione da qui e esegui test in autonomia."
CI has no Windows runner, so v1.1.0 shipped without these checks. They ran on the owner's Windows PC:
Chronos.Core.Windows.Tests: 96/96Chronos.App.Tests, including the classes that used to hang on this PC: 974 passed, 1 skipped. Five stale tests were fixed..gitea/scripts/installer-test.ps1(install, upgrade, add/remove a program, legacy Uploader and Server 1.0). Not run. This PC has Chronos 1.0 installed for all users, so the script would ask UAC to upgrade the owner's install (DECISIONS 2026-11-16). It belongs on a clean Windows PC or VM.Fixes found go into milestone v1.1.1: PR #71, released as
v1.1.1. The user data in%LOCALAPPDATA%\Chronoswas backed up toB:\chronos-tmp-wintest\localappdata-backupand never touched.Progress (2026-11-16), PR #71:
Done:
Chronos.Core.Windows.Tests: 96 passed.Chronos.App.Tests: 5 stale screen smoke tests fixed, now 969 passed and 1 skipped. Fixes:Blocked:
installer-test.ps1: this PC has Chronos 1.0.0 and Uploader 1.0.0 installed for all users (Program Files). With no per-user entry, the setup finds that install and asks UAC to upgrade or remove it. Run it on a clean Windows. The real 1.0 → 1.1 upgrade on this PC needs the owner's UAC approval.Hands-on GUI test of the portable 1.1.0 on the dev PC (2026-11-16):
/healthok,/admin/200;share: Sharing stopped,app: Chronos exiting).Chronos-Setup-1.1.0.exestarts unelevated. Its pages were not inspected (screen access not granted), and it was closed without installing.Findings fixed in this branch: