Launching today
Adoptest
A test suite for documentation
5 followers
A test suite for documentation
5 followers
Reproducible documentation checks. A model reads the material. Docs don’t fail loudly. They just quietly stop matching the product, and nobody finds out until a customer follows step 4 and it isn’t there anymore. Every tool I tried told me a page was old. None told me it was wrong. Adoptest links a page to whatever it was written from, then watches that source. Approve once, and it stays silent. Private beta. Looking for teams who’ve been burned by a doc that lied.
Launch Team
Render Sandboxes: a computer for every agentIsolated compute, persistent state and a real filesystem
Promoted
1. Before Adoptest, how did you find out a page had gone wrong?
A customer or colleague told us
A support ticket traced back to it
Scheduled review or audit
Someone happened to notice while working on something else
We usually didn’t find out
2. Where does your documentation actually get written from?
Tick all that apply.
Release notes or changelog
Jira tickets
Recorded calls or demos
Slack or Teams threads
A spec or requirements doc
Someone’s notes or spreadsheet
Straight from the product, no source document
3. Has Adoptest caught a page you would have missed?
Yes, and I can name it
It flagged things, but we already knew about them
It flagged things that turned out to be fine
Nothing yet
If yes, which page, and what was wrong with it?
4. Are there pages you’d never want alerts on?
Archived or deprecated content
Drafts and work in progress
Internal-only spaces
Pages owned by another team
No, alert me on everything