Tricentis qTest StrawberryRead every defect, draft every requirement, approve in one pass
One sentence in, and a companion has been through the Tricentis qTest defects, put them where you can read them, and marked the ones it was not sure about.
Open the defect. Check it against something else. Write the change. Move to the next one. That is the Tricentis qTest afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a defect until you approve it.
What it can do is exactly what Tricentis qTest exposes to an account you authorise and nothing beyond it: 6 operations, 2 reads and 4 writes. In practice that means it can update a requirement, update a defect and submit a defect, and work across the defects and requirements.
The Tricentis qTest API stops at Tricentis qTest. 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.
What does it already know about your requirements?
2 of the 6 operations are reads.
Your account, not a guess at it: a companion can get a requirement and get a defect, and the full list below is the whole list, with nothing inferred from Tricentis qTest's documentation.
The defects are what most of this inventory is about, alongside the requirements. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of Tricentis qTest admin becomes a queue you review.
- Get Requirement
- Get Defect
Can it change a defect without asking?
All 4 write operations wait for you.
A companion can update a requirement, update a defect and submit a defect, and each one is staged on an approval card first: you see the defect, the field and the new value before it lands in Tricentis qTest.
Nothing in Tricentis qTest is sent, changed or deleted on your behalf without that click, and a rejected card leaves the defect exactly as it was. The gate is the same one on every surface, described at security.
- Update Requirement
- Update Defect
- Submit Defect
- Create Requirement
Can it get requirement every morning by itself?
Yes.
Saved as a routine, the Tricentis qTest defects 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 site work, the Tricentis qTest defects 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