# Retest log — build 43

## Fixes to confirm (FIX)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| FIX-01 | The reported bug no longer happens | The issue as it was reported: its steps, its platform, and a build that contains the fix | 1. Check the version or build number on the device matches the build with the fix. 2. Follow the steps from the original report exactly, with the same kind of account and data. | What the report said should have happened now happens. The original error, crash or wrong result does not appear. | | | |
| FIX-02 | The fix holds with different data | As above | 1. Repeat the original steps with a different account, item or value from the one in the report. | The same correct result. The fix is not tied to the one example in the report. | | | |
| FIX-03 | The fix reached every platform the issue affects | The issue lists more than one platform | 1. Repeat FIX-01 on each platform the issue lists, on a build of that platform that contains the fix. | Each platform shows the correct behaviour. A platform whose build has not shipped yet stays untested, not passed. | | | |
| FIX-04 | A fix that changed a message reads correctly | The fix changed text, an error or a label | 1. Trigger the message the fix changed. | The new wording appears in full, is not cut off, and makes sense to someone who has never seen the bug. | | | |

## Around each fix (NEAR)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| NEAR-01 | The rest of the screen still works | A build that contains the fix | 1. Open the screen where the fix was made. 2. Use every other button, field and link on it. | Everything else on the screen behaves the way it did in the last release. | | | |
| NEAR-02 | The other ways into the same feature | As above | 1. Reach the fixed feature from each other route: a notification, a link, the back button, a fresh launch. | The fix holds whichever way you arrive. | | | |
| NEAR-03 | Anything that shares the changed code | The developer's note on what the fix touched | 1. Run the checks for the other screens the developer named. | They pass as before. If nobody can say what the fix touched, run the never-break group in full. | | | |

## Never break (CORE)

| ID | Journey | Preconditions | Steps | Expected result | WEB | AND | IOS |
|---|---|---|---|---|---|---|---|
| CORE-01 | Sign up | No account for the email you will use | 1. Create an account end to end. | The account is created, the verification email arrives, and the app opens signed in. | | | |
| CORE-02 | Sign in and sign out | An existing account | 1. Sign in. 2. Sign out. | Both work. After signing out, the back button does not show signed-in screens. | | | |
| CORE-03 | Reset a password | An existing account whose inbox you can open | 1. Run the reset flow to a new password. 2. Sign in with it. | The new password works and the old one does not. | | | |
| CORE-04 | The one thing the app is for | Signed in | 1. Complete the main journey end to end. | It completes with the result a customer would expect. | | | |
| CORE-05 | Take a payment | Signed in. A test card that will succeed | 1. Pay for something. | The payment succeeds once, the receipt matches the total, and nothing is charged twice. | | | |
| CORE-06 | Update over the previous version | The previous release installed and signed in | 1. Install this build over it. 2. Open the app. | Still signed in, data intact, and no second onboarding. | N/A | | |