Bugster

191 posts

Bugster banner
Bugster

Bugster

@bugsterdev

The AI QA Engineer. Backed by 500 Global

San Francisco Sumali Aralık 2023
531 Sinusundan963 Mga Tagasunod
Bugster nag-retweet
Juan Beck
Juan Beck@JBautistaBeck·
De nada sirve crear un test rápido... Si correr la suite completa te lleva horas. La verdadera agilidad no es automatizar una prueba aislada. Es tener la confianza de lanzar toda tu regresión cada vez que subís a producción, sin frenar al equipo de desarrollo.
Español
0
1
2
195
Bugster nag-retweet
Juan Beck
Juan Beck@JBautistaBeck·
Automatizar QA no debería llevar semanas... Grabé este video para mostrarles cómo crear un test de carrito de compras en Bugster usando solo texto. Menos de 60 segundos. El agente de IA entiende el flujo de su web, ejecuta los pasos y guarda el test sin que tengan que programar ni mantener scripts frágiles. Cero código.
Español
0
1
3
198
Bugster nag-retweet
nacho solorzano
nacho solorzano@naquiaos·
Wrapping Up 2025: The Year of Agents They called it "the year of agents." They were "absolutely" right. What we saw at @bugsterdev :
nacho solorzano tweet media
English
2
2
10
780
Bugster nag-retweet
nacho solorzano
nacho solorzano@naquiaos·
Catching bugs is half the job. The other half is fixing them fast. Now when @bugsterdev finds an issue, you can click "Fix in Cursor" and jump straight to the code. No context switching. No copy-pasting error messages. See the bug, click, fix, keep shipping. Took 5 minutes to build. Small quality-of-life improvement that saves time on every failure.
English
0
3
7
547
Facundo
Facundo@faculopezscala·
Claude Code for testing. @bugsterdev Launch Week Day 4: Interactive Shell. Ask Bugster to test flows, save tests, run suites, and explore features with agents, all inside your IDE.
English
5
4
12
989
Bugster
Bugster@bugsterdev·
The testing workflow developers actually wanted: → Ask questions in natural language → Generate tests on the fly → Run everything from your IDE Interactive Shell is here 🔥
Facundo@faculopezscala

Claude Code for testing. @bugsterdev Launch Week Day 4: Interactive Shell. Ask Bugster to test flows, save tests, run suites, and explore features with agents, all inside your IDE.

English
0
0
5
283
Bugster
Bugster@bugsterdev·
Your CI ran. But you found out 3 hours later 🔕 Day 3 Launch Week: Slack Integration. Bugster now pings your team the instant tests finish. No more checking dashboards. Instant results in Slack.
Franco Sebastián Benítez@francosbenitez

Your CI tests passed. Or failed. But you only found out 3 hours later. Day 3 of @bugsterdev Launch Week: Slack Integration. Bugster can now ping your team the moment tests finish running. Pass or fail, you'll know instantly—right in Slack. One click to connect. Pick your channel. Choose if you want all results or just failures. Done.

English
0
0
2
545
Franco Sebastián Benítez
Franco Sebastián Benítez@francosbenitez·
Your CI tests passed. Or failed. But you only found out 3 hours later. Day 3 of @bugsterdev Launch Week: Slack Integration. Bugster can now ping your team the moment tests finish running. Pass or fail, you'll know instantly—right in Slack. One click to connect. Pick your channel. Choose if you want all results or just failures. Done.
English
2
3
9
1.1K
Bugster
Bugster@bugsterdev·
We wrote a step-by-step guide on how to implement this MVP roadmap using Bugster. The best part? Our free tier should be enough to get your first 5 critical flows running. No budget. No QA team. No excuses. Check the docs 👇👇
nacho solorzano@naquiaos

You don't have a speed problem. You have a confidence problem. shouldideploy.today If you've never seen it, it's a joke site. Enter on a Friday, the answer is always no. The problem? For a lot of teams it's not a joke. It should be a yes. Every day. 5 e2e tests on critical flows fix that. We built an MVP roadmap to get there without big budget or a dedicated QA team. Link in the comment.

English
1
0
4
342
Bugster
Bugster@bugsterdev·
Claude Code (@claudeai) but for testing?
Bugster tweet media
English
1
2
5
659