Booking module testing: screenshot capture checklist

Open the formatted screenshot checklist.

Use with the complete end-to-end testing tutorial. Revision: 4 November 2026.

Screenshots are not required to complete the written test specification. They will make the illustrated tutorial easier to follow. Capture the core states below using a deployed staging build whose version is recorded. If a required screen is missing, report the missing state instead of fabricating an example.

#Capture settings

• Use fictional records matching the guide: MyClinic QA, Dr Alex QA, Alex QA, Sam QA, Consultation QA and the stated financial fixtures.
• Prefer desktop captures at roughly 1440px width, normal browser zoom, with the relevant panel fully visible. Use a 360–430px-wide viewport for mobile examples.
• Save JPEG at quality 80–85 where text remains crisp, preferably no more than 1800px wide. Use PNG if JPEG makes dense labels unreadable.
• Use one focused state per image. If a page is long, capture separate numbered panels; do not shrink an entire page until its text is unreadable. Stitch only adjacent portions of the same unchanged screen when necessary.
• Crop unrelated browser chrome. Preserve the navigation needed to find the page, field labels, selected dates, status and expected amounts.
• Mask phone/email details, sender identifiers, access tokens, receipt/recall/proposal tokens, secrets and unrelated notifications. Do not expose tokens in the address bar or QR codes that grant real access.
• Keep treatment and payment fixtures separate: pricing adjustment is ₹53,000, while the payment ledger is ₹50,000. Capture each image with the appropriate fixture.
• For handset evidence, show the workflow message, clinic-local timestamp and whether it is the patient or provider test phone. A settings screenshot cannot prove receipt.
• Supply a short manifest: filename, deployed commit/version, capture date/time with timezone, case ID, screen state and any masking performed. Keep full unmasked evidence in the authorized test system only.

#Core tutorial images

Capture these first. The filenames indicate where the future article assets should be placed; the article does not reference nonexistent images today.

The first documentation pass can use S01, S03–S06, S09–S11, S13–S18, S20–S21, S24–S26, S29, S31–S33 and S35–S36. The remaining core captures add detail to the corresponding workflows.

#Additional regression and integration images

These are useful evidence or troubleshooting illustrations; capture them after the main flow is correct.

Existing images under /docs/booking-whatsapp/ can illustrate sender selection, template editing, linking and delivery settings if they match the deployed build. Do not reuse a failed-message screenshot as evidence of successful delivery.

#Handover

Send the filenames above with the capture manifest. For a broken state, include the case ID and expected/actual difference; keep that image as defect evidence until fixed. Once supplied, insert verified images beside the relevant tutorial case with descriptive alt text and confirm that each published asset URL loads. Image links must not be added before files exist.