The principle you are checking
The web app saves failed requests that change data, that is POST, PUT and PATCH, in the browser's IndexedDB queue when there is no network, and replays them once it returns. Each of them gets an idempotency key in its header, so a repeated send does not create a duplicate on the server side.
The queue also handles files and forms, and its state is visible to the user: waiting, syncing, error or login required. Acceptance means checking each of these behaviours on a real device, in a real workplace.
Preparing the trials
Use a test account, not an employee's account, and the device on which the app will be used. Prepare a list of three simple entries: a form without an attachment, a form with a photo, and an entry that ends in a validation error. Record the number of records in the system before the trial, because that number is the reference point.
Plan a place where there is really no signal, for example a hall or a cellar, and a spot nearby with a network, so you can move between them during the trial.
Example trial: records in the system before and after the network returns
- Before the network returns
- After the network returns
Trials and criteria for the result
Each point on the list has its expected result. Record any mismatch as an acceptance defect and pass it to the supplier. Remember that after a 4xx or 5xx error the idempotency key is released, and the server remembers only results completed with success 2xx, so a corrected entry can be sent again.
Retry delays grow according to the Fibonacci sequence, so after a longer outage synchronisation does not happen immediately when the network returns. Give the app time and watch the state of the queue instead of clicking again.
Two errors worth triggering on purpose
The first is an entry with a validation error: the queue should show the error state, not hide it. The second is an expired session: the request should enter the login required state and be sent after logging in, without losing data.
What to record in the acceptance documentation
The acceptance documentation is a short protocol: date, device, place of the trial, list of steps, the number of records before and after, and screenshots of the queue states. It supports the audit evidence that the app keeps data when the network is lost.
Also record the limits: without a network the browser cannot fetch new data from the server, and idempotency records are cleared after 13 days by default, so entries left in the queue for longer than that need a separate procedure.
Checklist
Video
Frequently asked questions
How many trials are enough for acceptance?
Three kinds of entries (ordinary, with a photo, with an error) and a trial of an expired session. Run each of them on the target device in a place without signal.
What does a correct trial result mean?
Exactly one record for each entry after the network returns, with no duplicates, and the queue state visible at every stage.
Who should carry out the trials?
The plant manager with a user from the hall, on a test account, so that no false entries are created on an employee's account.
Acceptance of offline work on your site
We will run the trials with the plant manager in a place without signal and prepare the acceptance protocol. Let us arrange a call.
Let's talk