10 lines
1.4 KiB
Markdown
10 lines
1.4 KiB
Markdown
# Draft across an application restart
|
|
|
|
WJ-036 runs the actual application behind a local HTTP gateway. Alice signs in and types a work entry. The gateway switches to maintenance and the Spring application closes, releasing its file database. Clicking Save in the existing form must expose the maintenance/reconnection message rather than report success.
|
|
|
|
A fresh browser tab receives the maintenance document taken from the provisioning script, HTTP 503, Cache-Control no-store and Retry-After 60. The application then starts again using the same database, and the public gateway resumes forwarding requests. The original browser must authenticate with its retained device credential and offer the original hours and description without a stored work entry or mutation receipt.
|
|
|
|
The fixture does not replace browser fetch responses or the draft implementation. It models the public gateway using a local HTTP server; it does not execute Hostsharing's Apache configuration or a production deployment. Operations tests cover deployment sequencing separately. The fixture uses an isolated database, captured email and disabled push.
|
|
|
|
Validation: all seven WJ-036 steps passed in the full local pipeline on 0.1.64-SNAPSHOT: 193 executed JVM tests including 19 browser examples, 41 filtered reports, 68 operations tests, 17 frontend tests and production/admin-recovery smoke. The completion push increments the version to 0.1.65-SNAPSHOT.
|