TestMonitor StrawberryRead every test result, draft every issue, approve in one pass
Your TestMonitor, worked while you do something else: 3 reads to go through it, 1 write to change it, and a card in front of every one of those changes.
Open the test result. Check it against something else. Write the change. Move to the next one. That is the TestMonitor afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a test result until you approve it.
What it can do is exactly what TestMonitor exposes to an account you authorise and nothing beyond it: 4 operations, 3 reads and 1 write. In practice that means it can create a test result, and work across the test results, issues and projects.
The TestMonitor API stops at TestMonitor. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the test results or ask you for them?
3 of the 4 operations are reads.
Your account, not a guess at it: a companion can find an a test result, find an a project and find an an issue, and the full list below is the whole list, with nothing inferred from TestMonitor's documentation.
The test results are what most of this inventory is about, alongside the issues. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of TestMonitor admin becomes a queue you review.
- Find a Test Result
- Find a Project
- Find an Issue
What happens before it can create test result?
The one write operation there is waits for you.
A companion can create a test result, and each one is staged on an approval card first: you see the test result, the field and the new value before it lands in TestMonitor.
Nothing in TestMonitor is sent, changed or deleted on your behalf without that click, and a rejected card leaves the test result exactly as it was. The gate is the same one on every surface, described at security.
- Create Test Result
Does the test result sweep have to be asked for every time?
Yes.
Saved as a routine, the TestMonitor test results pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the TestMonitor test results sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents