# Saved, then gone after a refresh: test that your app really saves

> A screen can show data that was never stored. One plain-language test creates a record, reloads the page and checks it is still there, the bug AI-built apps ship most.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/saved-then-gone-after-a-refresh/

## The screen is not the database

Modern apps update the screen before the server answers, so they feel fast. If the save then fails, or never happens, the screen keeps showing what you typed until you reload.

In apps built with AI this is everywhere, because the agent can make the screen look right without the storage being right: a missing database rule, a wrong table, a write that only lives in the browser. An audit of one such app listed, among 31 bugs, a [time tracker that reset on page refresh](https://www.bacancytechnology.com/insights/vibe-coding-testing) during an active session. The founder had been clicking through the main flows after every build session, and none of those clicks included a reload.

## The test

```text
Sign in with the stored account "customer".
Create a project named "QA release notes".
Reload the page.
Check that "QA release notes" is still listed.
Open it, rename it to "QA release notes v2" and save.
Reload again and check the name reads "QA release notes v2".
```

The reload is the whole point. A check that runs without one tells you what the page remembered, not what was stored. Testsy reads the value after each reload and keeps it in the result, so a pass says exactly what was on the screen and when.

The password for "customer" is not in the text. It is a [sign-in account](https://testsy.dev/docs/sign-in-accounts/) stored for the project; the tester types it into your sign-in form and the AI never sees it.

## A run of it

We ran the same idea on our practice site: sign in with the wrong password and see it refused, sign in properly, reload and check the session is still there, save a note, reload, and check the note survived.

![Screens from that run: the wrong password refused, the session still there after a reload, the note still there after a second reload.](https://testsy.dev/blog/img/web-session-screens.webp)

All 11 checks passed in 1 minute 31 seconds. Open [the run](https://app.testsy.dev/share/TdEMIxQQQlDqbCJ1MIQ0xXt9_X7S2KAl) (live until 18 February 2027), and read the full write-up: [Test that sign-in and saved data survive a reload](https://testsy.dev/blog/test-that-sign-in-survives-a-reload/).

## Where else to reload

- **After editing**, not only after creating: an edit can update the screen and fail to save.
- **After deleting**: the item disappears from the list, then comes back on reload.
- **On a second device**: sign in as the same account in a new browser and check the record is there. A test can do this by opening the address again after signing out and in.
- **Settings**: change a preference, reload, check it held.

## Make it permanent

Save the test and run it after every change your agent makes, or every night on a [schedule](https://testsy.dev/docs/schedules/). The bug has a habit of coming back when the agent rewrites the data layer.

Start from the [create, edit and reload starter](https://app.testsy.dev/try?starter=record-persistence).

This post is part of [Testing an app you built with AI](https://testsy.dev/blog/test-an-app-you-built-with-ai/).
