Launching today
Seldon
Behavioral QA agents that use your product like customers do
58 followers
Behavioral QA agents that use your product like customers do
58 followers
Find the tests you didn’t know to write. Tell Wren what should work in plain English. Its QA agents try the paths your customers take, like going back to change an address halfway through checkout or retrying a failed payment. When something breaks, you get a replay and the steps to reproduce the bug. First 10 runs free.
Free Options
Launch Team
LoomShow, don't just tell with Loom
Promoted
Hey Product Hunt! I’m Tom, co-founder of Seldon. We built Wren because your entire test suite can pass and a customer can still find a bug five minutes after you ship.
We’re an applied research lab in SF. Our team includes researchers from MIT and Berkeley and people who’ve built products at Meta and Spotify. We put people and agents in front of the same screens and study where their decisions differ. That got us interested in a QA problem. A test can tell you whether the route you scripted works. Customers get to pick their own route.
How does Wren work?
Give it a goal in plain English, like “a new teammate should be able to accept an invite and join the workspace.”
Wren’s QA agents open your app and try different ways to reach that goal. One might open the invite while signed into the wrong account, switch accounts halfway through, and try the link again. You can test those paths without writing a separate script for each one.
When something breaks, you get a recording and the steps to reproduce it. You can run Wren alongside your existing tests in CI.
Who’s it for?
We built Wren for engineering and QA teams, from startups shipping new features every week to enterprise teams with years of test coverage. One early team told us Wren saved them days of QA before a release.
Try it on something you already test
Your first 10 runs are free. I’d start with a flow your team already has a passing test for. Did Wren catch something your suite missed? I’d love to hear what happened. We’ll be here all day.
Love this, @tom_charman!
Fun fact about how Wren started…
@marquise_rosier was on a customer call helping with something else when he spotted a problem nobody asked us to solve. He thought: we could probably build this. So we did.
A few weeks later, @dominic_kennedy shared some early feedback. Tests went from 10–15 carefully written steps to “go here, go there, click here. That’s it.” One design partner called it “a bit of a must.”
I remember that “wait, this could be something” moment.
Super excited we're opening it up for anyone to try. Can’t wait to see what folks break with it. 💛
cool launch!! the hard part is knowing if a weird path it found is a real bug or just something no customer would ever do
@igorblink Thank you!! 100%! That’s why we built Wren on behaviour models of real users rather than random clicking, so the paths it tries are ones customers actually take. And every finding comes with a recording, so you can go in and watch back to verify. Would love to hear what you think if you give it a spin!
Fun fact: Wren was developed using Wren
@mattpetersen3 I'd hope so! :)
Epic. This is all i need in my life right now. My team (and I) can't ship anything without missing serious flaws. Godsend.
@willsmercer I know that feeling. Someone breaks it five minutes after launch and suddenly the test you should’ve written feels painfully obvious. Would love to hear what Wren picks up on your next release!
congrats on the launch tom. the invite plus account switch example is a good one, those half finished flows are where real users get stuck and nobody writes a test for them. can wren start from a landing page and follow the whole signup from there?
@agshin_rajabov Hello Agshin, absolutely! Wren can sign up for your product, and tell you what about your signup flow caused the most friction! We even have customers presently using Wren as their weekly regression suite, running several dozens of test cases!
@agshin_rajabov Thanks so much! Yep, you can give Wren the landing page URL and a goal like “sign up and reach the dashboard.” It starts on that page, finds its way through signup and checks whether it gets there. If it gets stuck halfway, you can replay the run and see exactly where.
the wrong account invite example is a good test of a real onboarding flow
the replay needs to make it clear whether a failure came from the product or from the agent getting stuck operating it
@saad_el_gueddari Yeah, that’s exactly why Wren records the whole run. You can watch the agent switch accounts, see which account it accepts the invite with and where it lands. If the agent gets stuck trying to switch, you can see that too.