Stop Leaking API Keys in your AI Agent Logs: A Go Sidecar Approach Subtitle: The Hidden Privacy Leak in your AI Agents and why your LLM "Audit Logs" are a GDPR Nightmare 1. The Problem Everyone is building AI agents right now. Whether you're usi...

You spend 15 minutes filling out a long configuration form. You get a Slack notification, switch tabs, reply to a colleague, and grab a coffee. 30 minutes later, you come back to the form and click "Save". The page flashes. The login screen appears...

TL;DR: Basic uptime tools just tell you "It's down." I wanted a tool that tells me why DNS? SSL? App crash?, checks from Tokyo/NY, and validates JSON schemas. So I built OpsPulse. The "It’s Just Down" Problem Every developer has been there. It’s 3:...

The Problem: The "Zombie UI" You click "Submit". The database is writing data. The API is processing the request perfectly. The backend is healthy. But on the screen... nothing happens. The button still looks clickable. The cursor is still a pointe...

Moving Beyond "Localhost" Testing Until now, Debuggo has been a fantastic tool for manual testing. You spin up a proxy, connect your phone, and verify how your app handles a 503 error or high latency. It works great for ad-hoc debugging. But manual...

The "Localhost" Bias We've all been there. On your machine, the API responds in 5ms. The UI updates instantly. You click "Submit," the modal closes, and you move on to the next ticket. Status: Done. ✅ But on a user's 4G connection in a subway tunne...

Testing frontend error handling is a pain. You want to verify that your React/Vue app shows a nice "Retry" button when the API fails. Or you want to check if the Skeleton Loader looks good during a 10-second delay. The traditional way: Open Chrome ...

"It works on my machine." We've all said it. But does your bash script work when the third-party API takes 15 seconds to respond? Does your backend service gracefully handle a sudden spike of 503 errors from a payment provider? Writing a full mock ...

In previous articles, I talked about how I generate tests using LLMs, parse Swagger schemas, and fight against hardcoded data. But "naked" LLM generation has a fundamental problem: it is linear. The model often tries to guess the next step without un...

In my last posts, I talked a lot about UI tests. But the real meat and the real pain of automation often lies with the API. API tests need to be fast, stable, and cover 100% of your endpoints. "Simple," you say. "Just take the Swagger schema and run...

Previously I talked about how I was tired of "flaky" tests and how I'm using AI to generate test steps, saving hours of my time. I showed how I can create a 20-step E2E test in 6 minutes, just by describing it. But there's a problem. Even an AI can...

Ilya here again. In my Previous article, I explained my reasons for no longer generating code, but instead to parse plain English into steps that I store in a database. I did this because as the only QA on my team I was tired of wasting time writing...

Ilya here again. In my first article, I shared how I got tired of fixing old, "brittle" automation projects and decided to build my own AI-powered tool. Today, I want to share my first failed approach and how it led me to the architecture I use for ...

My name is Ilya, and I'm a QA Engineer. To be exact, I'm the only QA on my team. You know what that means. I handle regression, new features, talking to devs, and explaining "why this broke again." But this isn't a story about starting automation fro...