L18. Check and hand over your app

Write a My Day test report and prepare the project for someone else, allowing about 30 minutes. You need its working address and local files, plus a phone if you installed the app. Without a phone, record the device check as not performed.

Acceptance checking means confirming that a program does what was promised. For this app, that means three tasks, a correct counter, remembered selections and offline reopening.

In class

The teacher will show a report with actions, an expectation and an actual result. Together, we will repeat a scenario and choose a related check for a proposed repair.

Run one complete scenario

• In Notepad, create Documents\AI-practice\my-day-check.txt. Record the date, browser, device and app address. Keep this file outside the program’s public folder.
• Open the app and choose Start a new day. Record what actually happens. Expect three empty checkboxes and a count of 0.
• Tick the first and third tasks. Check both the count of 2 and the identities of the selected tasks. Untick the first: only the third should remain, with a count of 1. Reload: that same state should return.
• Try the keyboard: press Tab until the focus outline reaches the second checkbox, then press Space. The second and third tasks should now be selected. Also check that clicking a task’s large text label toggles it.
• Narrow the window and use the browser menu to increase zoom to 200%. All three labels and the button should remain accessible; vertical scrolling is fine. Return zoom to 100%.
• On the phone, open the app online and wait for offline readiness. Close it, disable both internet connections and reopen it from its icon. Change a selection, close and reopen once more. Record the result, then restore the connection.

[[VIS:b5_app_checks]]

Describe a problem someone can reproduce

Replace “nothing works” with the steps, expected result and actual result, as in the example below.

A practice entry in my-day-check.txt looks like this. It illustrates the report format, not your actual test result:

Check: reopening
Actions: selected 1 and 3; reloaded
Expected: same selections, count 2
Actual: all tasks unchecked, count 0
Address: HTTPS, normal browsing window

• If a test fails, first copy the working folder to my-day-backup. If that copy already exists, use my-day-backup-2 or the next unused number. Paste your report and the relevant file’s contents into the AI message. For a saving problem, use app.js; for an offline launch failure, include the contents of sw.js and manifest.webmanifest.

> [PROMPT]

> Here is my bug report and current My Day code. Identify the most likely cause supported by this information. Suggest one check before editing. Once confirmed, return only the complete files that need changes and explain which test to repeat. Preserve the three tasks, manual new-day button and relative paths. Do not add features.

• Save the complete revised files in your local my-day folder, replacing their old versions. Before publishing, update the cache number in sw.js as in lesson 17: caching applies to browser tabs as well as installed app windows. Save sw.js. In the repository, choose Add file → Upload files, upload the changed files including the revised sw.js, then Commit changes. Wait for deployment. Open the app online, close all its windows, then reopen it.
• Repeat the failed check and one related scenario. If you repaired saving, also test the new-day button: it must save [false,false,false], clearing the selections while keeping all three tasks.

> [FIX]

> Fixed on the computer but still wrong on the phone? Check the address and cache version. Open online, close all app windows, then reopen.

Prepare a clear handover

Place a README.md beside the seven files. This is a plain-text description: the app’s name, how to open it, what the new-day button does, where data lives, and how to update the cache. The supplied ZIP already includes one. Add your link and actual test status, such as “Edge: passed; Android: not yet tested”. Share the files without passwords or access tokens.

Home practice

• Copy my-day beside the original as my-day-test-home; add an unused number if needed. Show filename extensions and rename the copy’s app.js to app-held.js.
• Open the copy’s local index.html and select a task. In Documents\AI-practice\home-bug-report.txt, record the action, expected count and actual result. Test only counting, not saving.
• Restore the name app.js, reload and repeat. Record the result after restoration. Success means someone else can reproduce both states from your report. Keep the main folder unchanged.

Self-test

• What three things are missing from “it broke”?
• Saving now restores the count of 2. Which related action should you check?
• Can you write “Android tested” after merely narrowing an Edge window?

Terms

• Test scenario: a sequence of actions with a defined expected result.
• Regression: a new failure in something that worked before an edit.
• README: instructions to read before using a project.