Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Are your tests actually verifying what your app is supposed to do, or just mirroring code you already wrote? 🧐 Feed business rules, design docs, and user personas into Gemini in Android Studio to generate tests that validate true requirements →

18,240 Aufrufe • vor 3 Tagen •via X (Twitter)

2 Kommentare

Profilbild von Dipak Kr Prasad
Dipak Kr Prasadvor 2 Tagen

Tests that just mirror the implementation are how regressions sneak past green CI. Feeding personas + design docs first is closer to how I'd brief a human QA. Have you tried this on a Flutter or Compose screen where the bug was a missing rule, not a missing assert?

Profilbild von BIFORGE Studios
BIFORGE Studiosvor 3 Tagen

This is something I keep running into. A test can be green and the game can still feel wrong. Testing the intended behavior instead of the code itself makes a lot more sense.

Ähnliche Videos

What they don't tell you about vibe coding: • Moltbook exposed 1.5M auth tokens. The owner hadn't written a single line of code. • Tea App leaked 72,000 government IDs. The database was just open, no sophisticated hack needed. • A researcher took control of a journalist's computer through her own vibe-coded game, without a single click. The code ran fine in all three cases, tests passed, reviews looked clean, and nothing raised a flag. That's the problem nobody is talking about. Teams are shipping faster than ever. AI writes the code. CI catches build failures. Tests catch regressions. Observability catches outages. But nobody is asking the one question that actually matters: What can an attacker do with this, right now? Because the bottleneck is no longer writing code. It's understanding what that code actually exposes once it's live. PR reviews miss auth edge cases. Unit tests don't probe broken access control. Staging environments don't simulate adversarial behavior. And business logic flaws look completely fine until someone decides to break them on purpose. Strix is an open-source tool that fills this gap. It reviews your running app the way an attacker would: - Crawls the app and maps every exposed route and flow - Probes abuse paths dynamically, not just at build time - Returns findings with proof-of-concepts and suggested fixes Strix was benchmarked against 200 real companies and open-source repos, where it found 600+ verified vulnerabilities including assigned CVEs. It's designed to fit into how modern teams already work. Run it before a release, after major changes, or continuously as the app evolves. If your team is shipping AI-generated code and you don't currently have a way to answer "what does this actually expose", it's worth looking at. GitHub link in the next tweet.

Akshay 🚀

52,399 Aufrufe • vor 5 Monaten