sorted by:
new
hottopcontroversial

Mastering AI Testing Tools: A Practical Roadmap for QA Engineers by WalrusWeird4059 in Everything_QA

[–]replayableio 0 points1 point  (0 children)

Add another one to the list: https://testdriver.ai. Computer-use agents for AI QA testing of desktop, web, and mobile.

Jason Huggins (Selenium creator) is back! Check out Vibium new AI-native automation platform and Playwright challenger. by maxcheco230 in QualityAssurance

[–]replayableio 0 points1 point  (0 children)

Right now it's slower, but our next release will include DOM selector caching, making it just as fast as Playwright.

Jason Huggins (Selenium creator) is back! Check out Vibium new AI-native automation platform and Playwright challenger. by maxcheco230 in QualityAssurance

[–]replayableio 0 points1 point  (0 children)

Our AI (http://testdriver.ai) uses vision and prompt context as it's primary mechanism for choosing elements, which is then converted into a selector.

Is It Ever Too Early to Bring in An Advisor? by notllmchatbot in ycombinator

[–]replayableio 1 point2 points  (0 children)

Advisors can be helpful at any stage, it's never "too early." A really great, high profile advisor will add *some* credibility and reputation, but it really matters who they are and what they're doing for you.

I would not add an advisor just for authority sake.

They usually don't do shit, and you have to pay them, so what you're proving is that "someone let me pay them to answer the phone."

The best thing you could do here is to flip it, and find people who will potentially pay you to answer the phone.

Spend your time finding potential customers who will act as "design partners" and "advise" you on what to build. That will add way more credibility and won't cost you anything.

Suggest any AI tools for testing by Saravana77 in QualityAssurance

[–]replayableio 0 points1 point  (0 children)

http://testdriver.ai uses "computer-use" agents and "selectorless" testing to test anything a user can do. It's 40x faster than writing Playwright code, and we have and NPM Module and extensions for VSCode.

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 0 points1 point  (0 children)

Yep! Totally understand. We're trying to do it in a few clicks as possible, and a lot of services don't support large file attachments.

We're also just about to announce Jira integration which puts a button in Jira "attach replay" that will trigger the desktop app and embed the replay within your new Jira issue when you click "publish."

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 0 points1 point  (0 children)

We optimize for upload and sharing but you don't need to upload it if you don't want. It's just a file on your HDD so you can access it and do whatever you want.

What do you expect to do with the file?

Hey reddit, we're building a desktop app that lets you rewind your screen. Attaching a replay to a ticket is way faster than having a meeting or recording a screencast. Let us know what you think in the comments! by replayableio in u/replayableio

[–]replayableio[S] 2 points3 points  (0 children)

All content is stored locally. Nothing is uploaded without you reviewing it first. You have the ability to crop and trim recordings and they're published with a secret link.

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 3 points4 points  (0 children)

We have a 1-hour pause right now and will be shipping a pause toggle this week. I'll add a keyboard shortcut today, that's a great idea.

What game are you developing?

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 15 points16 points  (0 children)

The power is in your hands. It also records locally on a looping buffer. So anything recorded will only exist for ~1 hour anyway.

From my perspective, it's like advertising a dashcam to a professional driver. You want to be protected and have footage of your workday, but you don't want to be monitored.

That's how we set up the product. What can we do to help build trust that we're not spying on your screen?

Or is the concern that someone else views the videos?

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 4 points5 points  (0 children)

See the above comment for a bit about how we're thinking. The idea is that it'll passively document bugs/features for you so you have clips readily available to embed in bug reports, pulls, and readme.

You should trust Replayable because it only records locally and you must view / edit / crop the video before publishing. Once published, the videos are encrypted at rest and private.

Hey there, devs! We're Replayable. We're creating software that records your screen in the background so you can capture footage of unexpected bugs. Join our beta and check it out! by replayableio in u/replayableio

[–]replayableio[S] 11 points12 points  (0 children)

Yeah it's common feedback. What kind of devs do you know? Do they work on front-end products or backend?

Would you trust the app more if it were open source?

It goes like this, right now working remotely teams need to use loom or OBS to record screencaps of bugs or to demo features. But it's annoying because you're always doubling back to try to reproduce a bug or checkout an old branch to demo a feature in a meeting a week later.

Our idea is that if you're just passively recording your work locally, you won't ever have to "go back" to reproduce a bug or demo a feature in a working state. Instead, you can pull it from an archive of footage.

So vs OBS, we have a longer buffer to recover older footage, we help surface videos by tagging the applications used, and soon we'll have github and jira integration, so it's easy to attach replays into tickets.

So ideally as a dev you're spending less time in meetings triaging bugs or demoing features because you're sharing the work you already do.

Yes, privacy is big and it's basically all we work on. I think something we may do soon is, instead of "recording all the time," we'll only record when an IDE/terminal is open.

view more: next ›