正在加载视频...
视频加载失败
Introducing CodeRabbit Verify Don't let your users be the first test run! > PR testing: catch broken features before merge > User journeys: confirm critical flows work before each release > Tickets and fixes: get reviewed, tested fixes for reported bugs In public beta now!
207,247 次观看 • 5 小时前 •via X (Twitter)
39 条评论

finally making sure all vibe-coded in 5 hrs apps are actually secure & usable

Rabbits together strong 🔥

amazing!!! our users were never meant to be the QA team. congrats on launch!

Wow, testing user journeys automatically before each release saves so much stress.

user journeys is a goated feature

glad you think so!

how do you guys even sleep with how fast you ship updates

many talented people, you should see if theres a role for you

it's really awesome!

Ohh very excited to try this

This is exactly what we need with so much lazy code out there! Automating QA is a solid start to fixing that mess. Great work, team!

vibe coders about to find out what testing is

Agentic security 👀

👀

Already tested on my long forgotten app, surprisingly everything works!! Congrats on the launch, team! 👏👏👏

LOVE THE ORANGE!

SAME

Nice, checking it out today!!

let us know what you think!

testing should move as fast as coding

user journeys confirmed before each release in public beta, vibe coders deserve this

how does CodeRabbit Verify handle complex user journeys where multiple features and external APIs need to work together?

Game-changer! Automating testing and fixing bugs before production saves developers so much time.

watching tests run live in the browser is a nice touch can it also run scheduled user journey tests automatically?

Congrats on the launch! Automating QA would save me so much time. Curious, how does it handle workflows that require login or authentication?

Curious why cursor or replit won’t just provide this as part of their stack?

when verify proposes user journeys from the codebase, how does it handle flows that need a logged in user or test payment details?

Amazing! I'm keeping an eye on this one.

the live browser run is so good, finally i can see what the test actually clicked does it work for pages behind a login too?

A much-needed addition for developers

Checkout and login flows are where I'd use this first. Most breaks there come from a third-party piece changing, like a payment sandbox or an OAuth provider, so the test has to hit staging with real webhooks, not mocks.

on behalf of vibe coders, thank you 🥲

can Verify run reusable user journeys on a schedule?

Testing user journeys before every release is huge 🎯

Nice to see this!

"jarvis start using this"

this is what coding agents have been missing. can it test complex user journeys too?

A great step toward more reliable software, Catching bugs before users experience them is what smart development should look like. 🚀💻

does it test mobile apps too, or only web and API for now?
