See how it works
A guided replay of a real test run recorded on 13 Nov 2026. Nothing runs on the server here, so it is instant.
Logbook under test:
1. Input: what the framework is given
Not a file or a document: a running test copy of the e-logbook, accounts to log in with, and written permission to test it.
The system to test
- Address
- Type
- Web/server e-logbook
Test accounts
One per role; passwords are never shown in reports.
Written permission
- Authorized by
- Scope
- Valid until
Plus the E27 catalogue (all 41 items, each with acceptance criteria) and the security baseline (expected settings).
2. Process: what the framework does
- Check written permission; refuse if missing or expired
- Check the logbook is reachable
- Reset the test copy to a clean starting state
- Run the security tests: log in, write entries, try forbidden actions
- Record every request and reply as evidence (passwords hidden)
- Link each result to its E27 item
- Write the report
| Test | What it checks | E27 item | Result |
|---|
3. Output: what you get
The report lists every E27 item with its tests, expected behaviour, acceptance criteria, evidence and result. Switch the logbook above to compare the two runs.
Now try it live