# Testmorrow | Example testing report

DEMONSTRATION ONLY: fictional Orbit app. No client data.

## A saved change disappeared.

Priority: HIGH PRIORITY

A customer believes their project changes were saved, but the data is lost on refresh. The success message creates false confidence and repeated work.

## Expected

A successful save keeps the new project name after the page reloads or the customer signs in again.

## Actual

The interface shows “Saved”, but a reload restores the previous project name.

## Steps to reproduce

1. Sign in to the test version of the app as a project owner.
2. Create a project named “Launch plan”.
3. Rename the project to “Launch plan v2”.
4. Select Save and observe the success message.
5. Reload the page.
6. Check the name. It has reverted to “Launch plan”.

## Evidence

```text
PASS  project.created          201
PASS  project.name.edited      Launch plan v2
PASS  save.toast               Saved
FAIL  project.name.afterReload Launch plan

Reproduced: 3 / 3 attempts
Browser: Chrome / Desktop
Environment: Staging / fictional Orbit app
```

## Follow-up

Check whether the save actually updates the stored project name. Show a success message only when the change is saved. Test again after reloading the page and signing in again.

https://testmorrow.com/sample-testing-report/