| 1 |
The three version places say 0.2.0 and a test fails when they differ |
Pass |
pyproject.toml, flash_card.__version__ and Doxyfile say 0.2.0; tests/unit/test_version.py (3 tests) |
| 2 |
CHANGELOG.md has a [0.2.0] entry (menu bar, progress per word list, UTF-8 message) and [0.1.0] is unchanged |
Pass |
Read in the pull request #94 |
| 3 |
The upload limit of the git host is probed before the build with a draft release that is deleted afterwards, and the result is recorded |
Pass |
A draft release with a 1 MB random file was refused with 413 Request Entity Too Large; the draft and its tag were deleted (release and tag lists checked) |
| 4 |
The executable is built with --clean from the commit to be tagged and passes the smoke test of MIL-009 |
Fail |
Built with --clean from d7ca24d (25.8 MB). The first smoke run passed three cases (level screen window, embedded list, progress file with 999 cards at level 100); the list override case failed once because the simulated mouse click did not register, and in 3 of 8 reruns the same click was lost. The cause was not found: it may be the click automation (timing of the pointer and the focus) or a defect of the program. The checks were stopped at the Product Owner's request because they take over the desktop, and are to be repeated in a container or on an isolated desktop (MIL-013) |
| 5 |
The tag v0.2.0 is an annotated tag on that commit; v0.1.0 is not moved |
Fail |
The tag points to d7ca24d and v0.1.0 is unchanged (2c580cc), but the tag is lightweight: the push of my annotated tag failed on a connection error, and the release creation through the API then created a lightweight tag. Replacing it needs a force update of a tag, which is outside what an autonomous run may do without the Product Owner |
| 6 |
The release v0.2.0 is published with notes (new, unsigned, data folder rule, how to build) |
Pass |
Release page returns HTTP 200; notes say what is new, that the file is unsigned, the data folder and how to build |
| 7 |
When the probe did not allow it: the notes say so and the issue "attach the files" stays open |
Pass |
The notes state that the executable is not attached and why; issue "Create the release and attach the files" stays open |
| 8 |
README, CHANGELOG and the Install page of the wiki in three languages link v0.2.0; check-readme.sh exit 0 |
Pass |
Merged in #94; wiki republished |
| 9 |
pytest, ruff, mypy --strict, lint-imports and doxygen are clean; BC-001, US-001 and PP-001 reviewed Go |
Pass |
261 passed; RC-067 to RC-069 |
