Windows test package wintest-3: lead the tester through the desktop app on a real PC #36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "windows-wintest3"
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?
The Windows test package as published for the friend's PC as
wintest-3(ogc-messungen release wintest-3). It was built from the integration branchwindows-next; these are its eleven script commits, cherry-picked onto main now that #33, #34 and #35 are merged. No Rust code is touched.dist.shputs the setup into the test package, so part 3 runs by default. It also adds a small helper,tests/notification-state.exe(packaging/windows/test/notification-state.c), for H19, with its imports checked. The package is namedogc-wintest-<version>-<run>(OGC_WINTEST_RUN, default 3), so a tester does not mix it up with an older one.installer-test.ps1,app-test.ps1, dot-sourced byrun-tests.ps1, script version 4) leads the tester through the desktop app on a real PC. Each step is recorded in the report, as a check or as the tester's answer:--include-newwas switched on too, the script reports an error and skips "Jetzt prüfen".ogc timer status, the task XML and the H23 schtasks questions. These include a throwaway probe task, which is removed in afinallyblock.ANLEITUNG.txtis rewritten to match (times, what changes, sending the report and screenshots, cleaning up).ps-test.shwith PowerShell 7 and fakes passes (191 checks).dist.shpasses with the app's bundle, including the installer under Wine.check.shpasses. The commits had a review with adversarial verification and a fix round before wintest-3 was published.