Launching today
Seldon
Behavioral QA agents that use your product like customers do
273 followers
Behavioral QA agents that use your product like customers do
273 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
Render Sandboxes: a computer for every agentGive every agent its own machine. Starts in under a second
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. 💛
@tom_charman The next big startup in San Francisco!
@dhaval_bhatt3 doing our best!
@dhaval_bhatt3 Thank you! its great to see all the support
@tom_charman I've been waiting for such a QA product for years. Back in the day, I hired non-engineer QA because I found they were better at breaking user flow and finding bugs that engineers wouldn't even consider.
NB: big fan of your branding, can you make a designer agent that creates experience users would like to have?
@samabrika1 Haha, thanks so much! That instinct for finding the one path nobody thought to test is exactly what we’re building into Wren. I’ll pass the branding love on to the team. And I should show you Finch at some point - it's built to make the lives of product teams and designers easier 👀
The "tests you didn't know to write" framing is what got me — as a solo dev I mostly hand-test the happy path and find the weird stuff from users after shipping. The half-finished onboarding flows are exactly where I'd point this first. One question: does Wren work on native apps too, or is it web-only right now? Most of what I ship is native, so that's the deciding factor for me.
@jcbuilds That's helpful to know! We're web only for now, but native is in the works and we’ll want early testers. If you're up for it, can we reach out when it’s ready?
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!
@tom_charman How does Wren deal with unexpected popups , loading delays, or interrupted user journeys ?
Ooo this is very useful, been looking for something like this.
Really like the section on the landing page with the "Old way vs New Way", it's excellent! Your approach in plain English looks soo much more seamless and intuitive when shown both versions side by side. Makes tests that much more fun to write lol. Bookmarked this and upvoted! Congrats on the launch!
@silvia_odwyer1 Cheers for the bookmark and the upvote! Glad the side-by-side landed. “What should the user be able to do?” is usually the easy bit to write down. Getting that sentence to work as the test was the fun bit for us. Doing our best to make QA fun (and simple)!
@silvia_odwyer1 Thank you for the message of support really appreciate it! This is exactly why we created it
@silvia_odwyer1 If you have your coding agent constructing the test cases and steps, it's still auditable and simple to follow
@silvia_odwyer1 Thanks you! Let us know if you've give it a try - would love to hear any feedback!
Fun fact: Wren was developed using Wren
@mattpetersen3 I'd hope so! :)
Tried this at a hackathon they hosted a few days ago. Very agent friendly. Great stuff
@benoni_esckinder - so glad to hear you had a good experience with it! Excited for some of the things we've out soon coming up too!
@benoni_esckinder thanks so much for joining our hackathon!! really glad to hear you enjoy the product -- we put a lot of work into making sure its a smooth experience 💨🙏🏾
@benoni_esckinder Thanks so much, and thanks for coming to the hackathon! So fun seeing what everyone was testing with it 🙌
@benoni_esckinder Thank you for giving us a go and trusting us with your code base - Great to hear you enjoyed using us !