Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Most apps look “done” in the editor. But what actually happens when a real user clicks through the app? I connected my PropertyBazaar project to Replay and ran Replay QA on it. It found a real issue with my newsletter form, no onSubmit handler, no subscription request, and no...

BharukaShraddha's profile picture

Shraddha Bharuka

36,155 subscribers

56,106 Aufrufe • vor 25 Tagen •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

30 Kommentare

Profilbild von Dhairya Karekar
Dhairya Karekarvor 25 Tagen

@replayio I’ll definitely try this on one of my projects.

Profilbild von Krishna Agrawal
Krishna Agrawalvor 25 Tagen

@replayio I’ve been looking for something like this. Will give it a try.

Profilbild von Aastha
Aasthavor 25 Tagen

@replayio This is exactly how QA should work. Finding real issues before users do 🙌

Profilbild von Neha Singh
Neha Singhvor 25 Tagen

@replayio Love this approach. Finding the actual root cause instead of just flagging the bug is super useful.

Profilbild von Ryan Zander
Ryan Zandervor 25 Tagen

@replayio This is the gap between a demo and a product. The UI can look finished while the main action quietly does nothing. Replay-based QA catches what screenshots miss.

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 25 Tagen

@replayio @BharukaShraddha yeah, it's wild how those things slip through until real users interact. replayio sounds super handy!

Profilbild von Dipanshu Kushwaha
Dipanshu Kushwahavor 24 Tagen

@replayio That's awesome! It's always good to see these kinds of things catch real issues. Glad Replay QA helped you out.

Profilbild von Vaidehi
Vaidehivor 25 Tagen

@replayio This is really useful. Catching these issues before shipping can save a lot of time.

Profilbild von Lyra Irish
Lyra Irishvor 23 Tagen

@replayio Great

Profilbild von Amber shaheryar
Amber shaheryarvor 25 Tagen

@replayio Monumental

Profilbild von Khushi Patil
Khushi Patilvor 25 Tagen

@replayio Sound interesting

Profilbild von Professional_Tech_AI
Professional_Tech_AIvor 25 Tagen

@replayio Impressive share

Profilbild von Zifan Carter
Zifan Cartervor 25 Tagen

@replayio Thanks for share

Profilbild von Raxon Tech
Raxon Techvor 25 Tagen

@replayio Great share

Profilbild von Max
Maxvor 25 Tagen

@replayio This is super cool! It's awesome that Replay QA helps catch bugs before they go live. Great work on this.

Profilbild von David Marco
David Marcovor 25 Tagen

@replayio AW that's

Profilbild von Saif Ai
Saif Aivor 25 Tagen

@replayio Great

Profilbild von Sagar Rahangdale
Sagar Rahangdalevor 25 Tagen

@replayio Great

Profilbild von Miles S.
Miles S.vor 25 Tagen

@replayio i’d 100% miss that newsletter bug in the editor

Profilbild von Sophia Nexus ⭐
Sophia Nexus ⭐vor 24 Tagen

@replayio Amazing post

Profilbild von aizah choudhury
aizah choudhuryvor 24 Tagen

@replayio Great share

Profilbild von John Smith Ai
John Smith Aivor 2 Tagen

@replayio Amazing

Profilbild von Aftahi Rahman
Aftahi Rahmanvor 24 Tagen

@replayio This is super helpful! Finding bugs before they reach users is key. Thanks for sharing your experience with Replay QA.

Profilbild von dhinna ship .ico
dhinna ship .icovor 25 Tagen

@replayio Form rendered without any submit handler attached

Profilbild von MARINA AI
MARINA AIvor 24 Tagen

@replayio Great share

Profilbild von Pushpendra Tripathi
Pushpendra Tripathivor 24 Tagen

@replayio Amazing

Profilbild von Jawad Rahman
Jawad Rahmanvor 24 Tagen

@replayio cool.

Profilbild von Abbas AI
Abbas AIvor 24 Tagen

@replayio Great share

Profilbild von Liam
Liamvor 24 Tagen

@replayio Amazing share

Profilbild von Dharmik Harinkhede
Dharmik Harinkhedevor 24 Tagen

@replayio Amazing share 💯

Ähnliche Videos

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay
0:57

My AI app looked ready to ship. Replay QA proved otherwise. Before launching, I connected the GitHub repo to Replay QA, let it run through the app like a real user, and within a few minutes it surfaced issues I would've never noticed by manually clicking around. What I liked most wasn't just finding bugs. It showed exactly what happened in the browser, explained the likely root cause, and gave enough context to fix the issue without guessing. Instead of running a one-time check, I connected the repo so Replay QA can keep testing every time I push changes or open a PR. No Playwright setup. No complicated pipeline configuration. Just a practical QA gate before users ever find the problems. If you're building with Cursor, Claude Code, Codex, Lovable, Bolt, Replit, or any AI coding workflow, this is worth adding before your next launch. Replay

Kaitee

64,294 Aufrufe • vor 1 Monat

I ran one of my own React dashboards through Replay before treating it as ready to ship. It looked fine to me. Replay QA found a notifications button that looked completely functional but did nothing when clicked, accessibility issues across the UI, and a workflow where completing a task failed to update the activity feed. Those are exactly the little things that are easy to miss when you're focused on building. With Replay for Teams, this kind of QA can also run around your team's GitHub workflow and surface debugging context as you ship. The app can look finished in the editor. What matters is what actually happens in the browser. Replay for Teams is launching today. Check it out on Product Hunt:
0:41

I ran one of my own React dashboards through Replay before treating it as ready to ship. It looked fine to me. Replay QA found a notifications button that looked completely functional but did nothing when clicked, accessibility issues across the UI, and a workflow where completing a task failed to update the activity feed. Those are exactly the little things that are easy to miss when you're focused on building. With Replay for Teams, this kind of QA can also run around your team's GitHub workflow and surface debugging context as you ship. The app can look finished in the editor. What matters is what actually happens in the browser. Replay for Teams is launching today. Check it out on Product Hunt:

Kaitee

57,558 Aufrufe • vor 25 Tagen

The harder part of QA on a team isn't always finding the bug. It's getting the finding in front of the right person with enough context to actually fix it. I tested Replay on ClientFlow, a React client-delivery dashboard I built. Replay caught an issue in the review workflow where approving work caused the status indicator to jump out of view. But the part I wanted to test was what happens next. With Replay for Teams, the QA findings are shared with the project, and teammates can be brought directly into the Bug or Test Run context instead of passing screenshots and explanations around. Find it → share the context → get it to the right person. That feels much closer to how QA should work when more than one person is shipping. Check out Replay for Teams on Product Hunt: Replay
0:40

The harder part of QA on a team isn't always finding the bug. It's getting the finding in front of the right person with enough context to actually fix it. I tested Replay on ClientFlow, a React client-delivery dashboard I built. Replay caught an issue in the review workflow where approving work caused the status indicator to jump out of view. But the part I wanted to test was what happens next. With Replay for Teams, the QA findings are shared with the project, and teammates can be brought directly into the Bug or Test Run context instead of passing screenshots and explanations around. Find it → share the context → get it to the right person. That feels much closer to how QA should work when more than one person is shipping. Check out Replay for Teams on Product Hunt: Replay

Iris Quinn

60,483 Aufrufe • vor 24 Tagen

I built a small tracker to manage my sponsored campaigns and invoices, then connected Replay QA to it before shipping any changes Dropped in my repo and it confirmed the connection instantly, no test suite written, no config Replay
0:32

I built a small tracker to manage my sponsored campaigns and invoices, then connected Replay QA to it before shipping any changes Dropped in my repo and it confirmed the connection instantly, no test suite written, no config Replay

Ace

119,301 Aufrufe • vor 24 Tagen

I present my newest project: "The Dogwatching Asymmetrical" There's still quite a bit to be done as there are still bugs, needed balance changes, and no real replay value you just kind of play for the fun of it right now here's gameplay footage #dogwatching #rblxdragfanart
2:19

I present my newest project: "The Dogwatching Asymmetrical" There's still quite a bit to be done as there are still bugs, needed balance changes, and no real replay value you just kind of play for the fun of it right now here's gameplay footage #dogwatching #rblxdragfanart

The Wooden Developer 🏳️‍⚧️

21,919 Aufrufe • vor 1 Jahr

MIT GAVE DEBUGGING ITS OWN FULL LECTURE -- BECAUSE MOST DEVS STILL HUNT BUGS WITH PRINT STATEMENTS LIKE IT'S 1995 54 minutes that take the thing you do every single day, badly, and show you the tools schools never bothered to teach. -> The moment it lands, you realize "add a print, run it, add another print" was never debugging. It was guessing with extra steps. Most people never learned the real toolkit. A proper debugger, breakpoints, tracing what the program actually does instead of what you assume it does. In 2026 guessing isn't good enough -> the bug is buried in code you didn't even write, and printf won't find it for you. An AI agent will generate hundreds of lines in seconds. When one of them quietly breaks, finding it runs on exactly the skills in this lecture. Anyone can add a print statement. The person who can actually trace a bug to its source is the one who ships while everyone else guesses. Bookmark & Watch it ↓
54:10

MIT GAVE DEBUGGING ITS OWN FULL LECTURE -- BECAUSE MOST DEVS STILL HUNT BUGS WITH PRINT STATEMENTS LIKE IT'S 1995 54 minutes that take the thing you do every single day, badly, and show you the tools schools never bothered to teach. -> The moment it lands, you realize "add a print, run it, add another print" was never debugging. It was guessing with extra steps. Most people never learned the real toolkit. A proper debugger, breakpoints, tracing what the program actually does instead of what you assume it does. In 2026 guessing isn't good enough -> the bug is buried in code you didn't even write, and printf won't find it for you. An AI agent will generate hundreds of lines in seconds. When one of them quietly breaks, finding it runs on exactly the skills in this lecture. Anyone can add a print statement. The person who can actually trace a bug to its source is the one who ships while everyone else guesses. Bookmark & Watch it ↓

slash1s

10,864 Aufrufe • vor 3 Monaten

This is the most meaningful announcement I have been part of in the Base ecosystem, a journey I have been on since day one. As a content creator who later added the builder tag to my identity, hearing this announcement while building my TravelMint mini app made it even more special. And listening to it with jesse.base.eth ’s excitement… That was the moment I felt proud of both myself and my project. Now it is time to work even harder, onboard more people to Base and accelerate the vision, infrastructure and reach of my project. Thank you to everyone who has supported me so far. Just as it is still day one for Base, it is still day one for both TravelMint and me. 🟦🇹🇷
0:41

This is the most meaningful announcement I have been part of in the Base ecosystem, a journey I have been on since day one. As a content creator who later added the builder tag to my identity, hearing this announcement while building my TravelMint mini app made it even more special. And listening to it with jesse.base.eth ’s excitement… That was the moment I felt proud of both myself and my project. Now it is time to work even harder, onboard more people to Base and accelerate the vision, infrastructure and reach of my project. Thank you to everyone who has supported me so far. Just as it is still day one for Base, it is still day one for both TravelMint and me. 🟦🇹🇷

Coinacci | coinacci.base.eth

14,541 Aufrufe • vor 9 Monaten

CLAUDE BUILT A TRADING SYSTEM ON MY MAC I gave Claude full control over my Mac and just left it running overnight No prompts, no detailed instructions – I just told it to figure out how to make money on Polymarket Then I closed the laptop and went to sleep In the morning, I opened my Mac and saw the terminal still running with logs constantly updating At first it looked like random activity, but once I scrolled through it, I realized it had actually built a structured system overnight It was already tracking wallets Ranking them by performance Filtering out the ones with random entries And focusing only on the ones with consistent behavior What surprised me the most is that it didn’t stop at analysis It organized everything into a working dashboard inside the terminal Capital, PnL, winrate – all updating in real time It even ranked wallets based on performance metrics like ROI, consistency, and execution timing This is the part I would normally spend hours building manually At that point, it was ready to trade, but not actually executing anything yet So I connected it to a Telegram copytrading bot to actually execute the trades, and just let it run Bot: Polymarket: After that, it started opening positions on its own A few hours later I checked the dashboard again Capital: $12,380 P&L: +$23,128 Winrate: 100% 48 trades executed Now I’m not even trading myself I just check the dashboard and see what it’s doing And the strange part is – it keeps getting better the longer it runs
0:24

CLAUDE BUILT A TRADING SYSTEM ON MY MAC I gave Claude full control over my Mac and just left it running overnight No prompts, no detailed instructions – I just told it to figure out how to make money on Polymarket Then I closed the laptop and went to sleep In the morning, I opened my Mac and saw the terminal still running with logs constantly updating At first it looked like random activity, but once I scrolled through it, I realized it had actually built a structured system overnight It was already tracking wallets Ranking them by performance Filtering out the ones with random entries And focusing only on the ones with consistent behavior What surprised me the most is that it didn’t stop at analysis It organized everything into a working dashboard inside the terminal Capital, PnL, winrate – all updating in real time It even ranked wallets based on performance metrics like ROI, consistency, and execution timing This is the part I would normally spend hours building manually At that point, it was ready to trade, but not actually executing anything yet So I connected it to a Telegram copytrading bot to actually execute the trades, and just let it run Bot: Polymarket: After that, it started opening positions on its own A few hours later I checked the dashboard again Capital: $12,380 P&L: +$23,128 Winrate: 100% 48 trades executed Now I’m not even trading myself I just check the dashboard and see what it’s doing And the strange part is – it keeps getting better the longer it runs

𝗖𝗛𝗔𝗜𝗡 𝗠𝗜𝗡𝗗 ⛓🧠

82,898 Aufrufe • vor 5 Monaten

From zero Grokbot experience to a working Mac app in 39 minutes. I recorded the whole thing. I've never used Grokbot before. But my friend Billy has and it seemed easy enough. My idea was app that locks me out of my inbox for 95% of the day. Forces me to clear emails between 5 AM and 10 AM or I'm done until tomorrow. I told Grokbot what I wanted Then: It signed into my Replit account Built a Chrome extension Built a Mac menu bar app Tested 23 different things 39 minutes later I had a finished product. Grokbot is the future of building software. You don't need to code. You don't need to hire developers. You just need to describe what you want and an agent builds it, tests it, fixes it, and publishes it. Billy Howell joined me on this call and gave me the Grokbot 101 materclass. He walked me through: - Why everyone on Twitter is using Grokbot for the wrong stuff - How to set up agent teams that work while your laptop's closed - The exact businesses you can start this week with a Shopify and a credit card - Why the window on this is short and you need to move now When you watch this and build something, tag it here. I want to hear what you're all building!
1:10

From zero Grokbot experience to a working Mac app in 39 minutes. I recorded the whole thing. I've never used Grokbot before. But my friend Billy has and it seemed easy enough. My idea was app that locks me out of my inbox for 95% of the day. Forces me to clear emails between 5 AM and 10 AM or I'm done until tomorrow. I told Grokbot what I wanted Then: It signed into my Replit account Built a Chrome extension Built a Mac menu bar app Tested 23 different things 39 minutes later I had a finished product. Grokbot is the future of building software. You don't need to code. You don't need to hire developers. You just need to describe what you want and an agent builds it, tests it, fixes it, and publishes it. Billy Howell joined me on this call and gave me the Grokbot 101 materclass. He walked me through: - Why everyone on Twitter is using Grokbot for the wrong stuff - How to set up agent teams that work while your laptop's closed - The exact businesses you can start this week with a Shopify and a credit card - Why the window on this is short and you need to move now When you watch this and build something, tag it here. I want to hear what you're all building!

Chris Koerner

31,902 Aufrufe • vor 8 Tagen

🚨 THIS IS ABSOLUTELY INSANE a developer just released a free tool that builds a vertical video with a talking presenter. out of one script and one photo. it's called lanshu-create-ai-presenter-video. it landed on GitHub two days ago. 267 stars. MIT. here's how it works: 1. You give it a script and a presenter photo you have the rights to. 2. The AI writes and voices the narration, generates the presenter, and locks the lips to the audio. 3. The skill edits, burns in subtitles and a cover, checks the sync, and hands back a master with a QA report. 9:16, 1080x1920, 30fps, 45-75 seconds. all of it happens in one run, on your own machine. save this before you sit down to cut your next video. i left the link in the next comment 👇
0:28

🚨 THIS IS ABSOLUTELY INSANE a developer just released a free tool that builds a vertical video with a talking presenter. out of one script and one photo. it's called lanshu-create-ai-presenter-video. it landed on GitHub two days ago. 267 stars. MIT. here's how it works: 1. You give it a script and a presenter photo you have the rights to. 2. The AI writes and voices the narration, generates the presenter, and locks the lips to the audio. 3. The skill edits, burns in subtitles and a cover, checks the sync, and hands back a master with a QA report. 9:16, 1080x1920, 30fps, 45-75 seconds. all of it happens in one run, on your own machine. save this before you sit down to cut your next video. i left the link in the next comment 👇

Granite

162,249 Aufrufe • vor 20 Tagen

The part people sleep on: ask your agent to help manage the portfolio after it's built. Set conditions, run it on a schedule, have it flag anything worth your attention. You get a push notification every time it trades and real-time P&L in the app, so you're never out of the loop.
0:50

The part people sleep on: ask your agent to help manage the portfolio after it's built. Set conditions, run it on a schedule, have it flag anything worth your attention. You get a push notification every time it trades and real-time P&L in the app, so you're never out of the loop.

Robinhood

83,659 Aufrufe • vor 1 Monat

I spent a week ignoring everyone who said to switch engines. Day 7, I pivot. You were right. Building GTA 6 with a loop of AI agents. I spent the entire day on one thing: Swapping the project out of Godot and onto Unreal. Yesterday I said I'd test Unity and probably skip Unreal. You guys pushed back hard: if you're serious about AAA, get on a real engine. so here we are. What a full day of "just setup" actually looks like: - Installed and configured Unreal - Fought it onto a Mac build (the metal toolchain nearly ended me) - Migrated the project over - Got into a real Map and building assets - Got a scene rendering with real lighting First time this actually looks like GTA instead of a prototype of it. I'm still wiring the agents into the editor and point the loop at a real engine. Feedback is appreciated!
1:49

I spent a week ignoring everyone who said to switch engines. Day 7, I pivot. You were right. Building GTA 6 with a loop of AI agents. I spent the entire day on one thing: Swapping the project out of Godot and onto Unreal. Yesterday I said I'd test Unity and probably skip Unreal. You guys pushed back hard: if you're serious about AAA, get on a real engine. so here we are. What a full day of "just setup" actually looks like: - Installed and configured Unreal - Fought it onto a Mac build (the metal toolchain nearly ended me) - Migrated the project over - Got into a real Map and building assets - Got a scene rendering with real lighting First time this actually looks like GTA instead of a prototype of it. I'm still wiring the agents into the editor and point the loop at a real engine. Feedback is appreciated!

Ziwen

86,302 Aufrufe • vor 2 Monaten

Just hacked my Ray-Ban Meta and built my own scanner with them The US has a lot of crazy products, so I built an app that explains what I’m seeing and where to buy it Used the Meta SDK to connect it with my smart glasses and test it in real life without looking like a freak
2:01

Just hacked my Ray-Ban Meta and built my own scanner with them The US has a lot of crazy products, so I built an app that explains what I’m seeing and where to buy it Used the Meta SDK to connect it with my smart glasses and test it in real life without looking like a freak

Juampi

124,073 Aufrufe • vor 2 Monaten

solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump touched $3m overnight and I slept through all of it my ticker, my github, my agents, and the market put three million on it while I was face down in a pillow people are betting on this thing because they can watch it get built in front of them. that's a weird kind of pressure and I love it not going anywhere, not selling anything, just building contract goes on chain today and the bot starts trading a real wallet with real money god bless
0:44

solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump touched $3m overnight and I slept through all of it my ticker, my github, my agents, and the market put three million on it while I was face down in a pillow people are betting on this thing because they can watch it get built in front of them. that's a weird kind of pressure and I love it not going anywhere, not selling anything, just building contract goes on chain today and the bot starts trading a real wallet with real money god bless

cvxv666

30,900 Aufrufe • vor 18 Tagen

🚨 Building AI agents is fun. Setting them up usually isn't. I expected to spend my afternoon configuring APIs, databases, deployments, and integrations. Instead, I spent it building the agent. That's what stood out after trying It removes a lot of the infrastructure work so you can focus on the workflow you're trying to automate. Definitely worth trying if you're exploring AI agents. Try Matagi free — no card needed.
2:12

🚨 Building AI agents is fun. Setting them up usually isn't. I expected to spend my afternoon configuring APIs, databases, deployments, and integrations. Instead, I spent it building the agent. That's what stood out after trying It removes a lot of the infrastructure work so you can focus on the workflow you're trying to automate. Definitely worth trying if you're exploring AI agents. Try Matagi free — no card needed.

Amy - AI Girl

37,973 Aufrufe • vor 2 Monaten

Kimi K3 dropped 3 days ago and i already used it to build my own PUBG the model that just took the number one coding spot on earth and it runs on a free tier no team no engine i just fed it free open models and assets that are already public and told it what i wanted it built the entire game itself the shooting the recoil the hit detection all of it came straight out of the model i barely wrote a line what youre watching here is the deathmatch mode and its already live battle royale is next im deep in it and the graphics get reworked right after i know it looks raw right now i wont pretend otherwise but the endgame is a build that runs perfect on phones and the moment its on mobile you drop ads in and it earns on its own the part that still gets me is my whole cost for this was a single subscription
0:22

Kimi K3 dropped 3 days ago and i already used it to build my own PUBG the model that just took the number one coding spot on earth and it runs on a free tier no team no engine i just fed it free open models and assets that are already public and told it what i wanted it built the entire game itself the shooting the recoil the hit detection all of it came straight out of the model i barely wrote a line what youre watching here is the deathmatch mode and its already live battle royale is next im deep in it and the graphics get reworked right after i know it looks raw right now i wont pretend otherwise but the endgame is a build that runs perfect on phones and the moment its on mobile you drop ads in and it earns on its own the part that still gets me is my whole cost for this was a single subscription

savip.

68,984 Aufrufe • vor 1 Monat

I started reading World Cup threads on Reddit for fun. Match reactions, ticket chaos, streaming complaints, travel questions and people yelling about things five minutes after kickoff. After thousands of comments, I realized I was still only seeing a tiny corner of it. So I let Matrix read the rest. It went through the tournament threads and pulled out the problems people kept raising again and again. That was the part that got me. It was not football noise. It was real user pain in real time. People saying what confused them. What annoyed them. What ruined the experience for them. What they wished someone had just made easier. No survey, no focus group, no polished feedback form. Just fans complaining in public, which might be the most useful market research on the internet. World Cup Reddit is basically a stadium full of product feedback. You think you are reading match threads. Look closer and people are already telling you what hurts, and half the time what somebody should go build next.
0:58

I started reading World Cup threads on Reddit for fun. Match reactions, ticket chaos, streaming complaints, travel questions and people yelling about things five minutes after kickoff. After thousands of comments, I realized I was still only seeing a tiny corner of it. So I let Matrix read the rest. It went through the tournament threads and pulled out the problems people kept raising again and again. That was the part that got me. It was not football noise. It was real user pain in real time. People saying what confused them. What annoyed them. What ruined the experience for them. What they wished someone had just made easier. No survey, no focus group, no polished feedback form. Just fans complaining in public, which might be the most useful market research on the internet. World Cup Reddit is basically a stadium full of product feedback. You think you are reading match threads. Look closer and people are already telling you what hurts, and half the time what somebody should go build next.

Iseunife The First

17,961 Aufrufe • vor 2 Monaten

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.
0:47

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 Aufrufe • vor 3 Monaten

I am keen to show you with a few lines of YAML config I am able to monitor my website and create a GitHub Issue if it is down by using the Open Source project Kestra Kestra is the Open Source Orchestration Tool with a large ecosystem of plugins, with these plugins you can connect them together like lego and building anything! Try it yourself, GitHub repo link below...
2:20

I am keen to show you with a few lines of YAML config I am able to monitor my website and create a GitHub Issue if it is down by using the Open Source project Kestra Kestra is the Open Source Orchestration Tool with a large ecosystem of plugins, with these plugins you can connect them together like lego and building anything! Try it yourself, GitHub repo link below...

Eddie Jaoude | DevRel | Open Source

16,864 Aufrufe • vor 1 Jahr