Adding Notes to Test Results
What notes are for
Load test results tell you what happened; notes let you record why. Use them to capture the context that is not in the charts: what was deployed, which environment was tested, what looked suspicious, what to try next. Notes live on the result page itself, so the context stays with the numbers instead of in a chat thread nobody can find later.
Notes are shared with your whole team: every member sees the same list on a test's results.
Where to find them
Open any load test result and switch to the Notes tab. The tab label shows how many notes the test already has, for example "Notes (3)".
The tab lists every note saved across all runs of that test, and each entry shows which run it belongs to, as the test name plus the run number. Selecting a note shows its full content in the Note details panel.
Adding a note
- On the Notes tab, click New Note.
- Give the note a title (at least 3 characters).
- Write the body in the rich text editor. Formatting like lists, bold text and links is supported.
- Click Add Note.
The note is saved against the run you are currently viewing, so observations stay tied to the exact run they describe.
Editing and deleting
Each note in the list has two icons:
- the pencil (Edit note) reopens the editor with the note's content; save with Edit Note
- the trash can (Delete note) asks for confirmation ("Remove this note?") before removing it
What to write down
A few patterns that pay off:
- Run context: "Run #12 was against staging with the new cache config, half the usual dataset."
- Observations: "Errors spike at minute 4, matches the DB failover window."
- Follow-ups: "Re-run with 2x virtual users once the connection pool fix ships."
- Verdicts: "Signed off for the Friday release, P95 within budget."
For version-related context that should be visible on the trend charts rather than in a list, use release tags instead; the two features complement each other.