SAMPLE REPORT

Desktop application

The report below comes from testing the Windows and macOS builds of an accounting program.

Cases tested: 288
Total findings: 25
Release blockers: 2

Test summary

288 cases were tested across two operating systems over four business days. 25 findings were reported; 2 could cause data loss.

Cases tested: 288
Total findings: 25
Release blockers: 2
Closed on re-test: 23

Severity distribution

2Critical

7High

11Medium

5Low

CLIENT: Anonymous · accounting software
PACKAGE: Release
DATES: 17–20 March 2026
ENVIRONMENT: Windows 11 · macOS 26 · 6 configurations

Coverage matrix

Each square is one configuration-scenario pair. Coloured squares carry findings.

PassedCriticalHighMediumLow

Finding cards

Five of the 38 findings in the report. Each card is exactly the format you'll see in yours.

4 / 4 showing

CriticalCNRY-302Updatewindows 11 · auto-update enabled

Auto-update corrupts the file that is currently open

Steps to reproduce

Open a large ledger file and leave it unsaved.
Trigger the automatic update.
Wait for the program to restart.
Try to open the same file.

Expected: The update waits for the open file, or the file is saved safely first.
Actual: The program exits mid-write; on reopening, the file cannot be read.
Impact: Unsaved work is lost permanently. Without a backup there is no way back.
Evidence: video-302.mp4 · corrupt-302.zip

CriticalCNRY-309Multi-userwindows 11 · two local accounts

A second user on the same machine sees the first user’s settings

Steps to reproduce

Sign in as user A and save the company details.
Sign out and sign in as user B.
Open the program and check the settings.

Expected: Each local user sees their own settings.
Actual: User B sees A’s company details and recent file list.
Impact: On shared machines, client information leaks to another user.
Evidence: video-309.mp4

HighCNRY-318Opening a filemacos 26 · 8 GB RAM

Files over 50 MB push memory past 4 GB and crash the program

Steps to reproduce

Prepare a 50 MB ledger file.
Open it and watch memory usage.
Switch to the reports tab.

Expected: The file opens and memory stays proportional to its size.
Actual: Memory reaches 4.2 GB and the program stops responding.
Impact: Users working with year-end files cannot use the program.
Evidence: memory-profile-318.json

MediumCNRY-327Syncwindows 11 · network drop

Offline edits disappear silently on the next sync

Steps to reproduce

Disable the network and enter three records.
Re-enable the network and wait for sync.
Check the records.

Expected: Offline records reach the server, or a conflict is reported.
Actual: The records are silently deleted with no warning shown.
Impact: The user never learns that data was lost. There is no conflict resolution.
Evidence: video-327.mp4 · sync-327.log

The report keeps living after handover

The web report is a link, not a dead PDF. Its status updates as you mark fixes, and after the re-test round every finding's outcome shows up in the same place.

A report for another product type

Website and web applicationE-commerce, SaaS panels, corporate sites — anything that runs in a browser.Mobile appiOS and Android, on real devices and real connections.API and backend serviceREST and GraphQL: contract, permissions, boundaries and concurrency.

Don't test the next release alongside your users.

Start a test Read a sample report