How We Test Tools
This page describes the actual process the editorial team runs before a single sentence of a review gets written.
What “Tested” Means Here
On R StackAI, “tested” means the editor personally signed up for the tool, ran a real workflow, and documented the result. Watching a promo video, reading a landing page, or talking to a vendor’s sales team doesn’t count — and it’s never presented in a review as if it did.
The Testing Process
- Access. The editor signs up on the tier that’s actually available to the platform’s readers — Free or a lower paid plan — not a vendor-provided Enterprise demo account.
- Testing log. Before writing starts, the editor records the version or plan used, how long testing ran, the specific tasks completed, screenshots or recordings where useful, and any limitations encountered.
- A real task. At least one task gets completed that matches a genuine reader scenario — building an actual automation, for example, not just clicking through the interface.
- Documenting limits. Anything that couldn’t be verified because of plan or access restrictions gets recorded separately and later flagged explicitly in the review.
- The “What We Tested” section. The published article states the testing scope openly — which plan, which features, how long — before the reader reaches any conclusions.
When Access Is Limited
Some features — Enterprise tiers, custom integrations, large-team functionality — aren’t accessible for hands-on testing without a corporate contract with the vendor. When that’s the case, the review says so directly, and information about those features is marked as sourced from official documentation rather than personally verified.
What We Don’t Do
- We don’t write a review based solely on marketing materials or press releases
- We don’t present vendor documentation as our own conclusion
- We don’t hide which features weren’t tested first-hand
- We don’t treat a vendor-provided demo account as sufficient grounds for a review’s conclusions
Internal Testing Logs
A testing log is kept for every published review and stored in an internal editorial record. It isn’t published in full, but it’s the source for the “What We Tested,” “Real Advantages,” and “Real Limitations” sections — and it’s the reference point when a review comes up for its scheduled retest.