Skip to content
Walkstamp

Use case

Test evidence an auditor will accept

You ran the test. Now you have to prove you ran it — with the screen, the clock time and what was observed. This is Walkstamp’s main case, and the only one where rejected evidence costs someone a whole day.

A page of the generated document, with the brand on top, the identification, and each screen next to what was said12
How the page comes out. What appears changes with the scenario: test evidence carries wall-clock time and a checksum; a work instruction carries neither.

Three things for the evidence round

Several cases in a single recording. Mark where one case ends and the next begins, and walk away with one document per case — or a single one split into chapters, with each one’s time in the spreadsheet.

Retest without recording it all again. The guided review walks the old document step by step and recaptures only the screens that changed. What stayed the same stays the same.

Redact everything at once. It reads the text on the screens, warns you when it finds a tax ID, an email or a card number, and covers every occurrence in one click — the redaction is burned into the image, not a layer on top. Reading the text needs a library fetched from the internet: on a network that blocks public CDNs it will not run, and the tool says so at that moment — redacting by hand still works.

Record evidence now free, no sign-up, and nothing leaves your computer

The pain

Print Screen, paste into Word, write the caption, repeat forty times. Two hours of manual work after a twenty-minute test — and the expensive part is not taking the screenshot: it is remembering what was being tested in each one when you come back to the document the next day.

And evidence gets rejected on detail. The clock time is missing, the step does not show the result, the header does not say which client it was, the image was cropped and the field cannot be read. The auditor does not argue the merit of the test: they hand the document back. Anyone who has had a pack returned on the eve of go-live knows the problem was never the test.

What comes out

A PDF (or Word, HTML, spreadsheet, ZIP) with one screen per step, in order, and nothing you have to type twice:

  • Clock time on every step, anchored to the real start of the recording — usually the make-or-break item
  • Your narration becomes the step note. You talk while you test and the text comes out written, paired with the screen of that moment
  • Identification header: test case, system and client, who ran it, ticket and result — and the file name already carries the case inside it
  • Redaction and highlights burned into the image: the covered ID number does not come back, and the arrow pointing at the field does not come off
  • Sensitive-data warning: the tool reads the text on screen and tells you which steps showed a tax ID, an email, a phone number or a card — and stops there, because sometimes that number is the proof
  • A hash per image and a verification package: whoever receives it checks in their own browser, at /verify, whether the images are still the same

How to do it

  1. Open the tool and pick the Test evidence use case in step 1.
  2. Click Record the screen and leave the microphone on. Narrate what you are doing: that is what becomes the description of each step.
  3. Run the test the way you would run it. The tool keeps a frame on every screen change and transcribes your speech alongside.
  4. Stop, discard the repeated screens, fill in case and ticket, and produce the PDF. Attach it in Zephyr, in Jira or on the ticket.

What it does not do — better to know up front

It does not read fields from SAP GUI for Windows. The browser receives an image of the shared screen, not the structure of the application. Capture picks up any window the operating system will share — Fiori, S/4 web, Ariba, SuccessFactors, Concur and the GUI itself all appear as an image — but with no field reading.

It does not guarantee compliance. 21 CFR Part 11, SOX, CSV and ISO 9001 are not features you can buy: the product produces the document with time, identification and verifiable integrity; compliance belongs to your company’s process. Anyone promising otherwise is selling what they cannot deliver.

It does not attach back into your test management tool. That would need an API and IT permission. What exists is the pre-filled link, which opens the tool with the case and the ticket already in place — and the way back is still dragging the file, which works in any tool.

Record evidence now See the plans

Everything above is in the free plan. What you pay for is the client brand on the document and the administration of a team — never the quality of the evidence.