Testmo StrawberryThe Testmo automation runs nobody wants to work through
Hand a companion the outcome. It reads the Testmo automation runs, does the 5-operation version of the job, and stops for your click on anything that changes a record.
Open the automation run. Check it against something else. Write the change. Move to the next one. That is the Testmo afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a automation run until you approve it.
What it can do is exactly what Testmo exposes to an account you authorise and nothing beyond it: 5 operations, 2 reads and 3 writes. In practice that means it can create an automation run, append to thread in automation run and append a to automation run, and work across the automation runs, project sessions and threads.
The Testmo API stops at Testmo. 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.
Where do the automation runs come from?
2 of the 5 operations are reads.
Your account, not a guess at it: a companion can list project sessions and list automation runs, and the full list below is the whole list, with nothing inferred from Testmo's documentation.
The automation runs are what most of this inventory is about, alongside the project sessions. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of Testmo admin becomes a queue you review.
- List Project Sessions
- List Automation Runs
Which automation runs wait for your approval?
All 3 write operations wait for you.
A companion can create an automation run, append to thread in automation run and append a to automation run, and each one is staged on an approval card first: you see the automation run, the field and the new value before it lands in Testmo.
Nothing in Testmo is sent, changed or deleted on your behalf without that click, and a rejected card leaves the automation run exactly as it was. The gate is the same one on every surface, described at security.
- Create Automation Run
- Append to Thread in Automation Run
- Append to Automation Run
What does the recurring automation runs pass look like?
Yes.
Saved as a routine, the Testmo automation runs 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 Testmo automation runs 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