This archive page collects articles on MockEvalio, a testing approach that simulates real-world user interactions to evaluate system behavior and performance. MockEvalio's importance lies in its ability to reveal critical flaws in software design and user experience, as demonstrated through our team's experiences with a problematic login button and a misfiring RAG pipeline.
18 articles since Aug 2026
A security review of MockEvalio found admin auth silently broken, a cross-tenant data leak, and a hardcoded key that traced straight back to the project's second commit, five months earlier.
I tested MockEvalio's new Stripe checkout end-to-end — real test card, real webhook signature. Three hours later, the buttons meant to get someone there were silently broken.
I built a complete system to measure whether MockEvalio's AI evaluator is accurate — comparison logic, deviation thresholds, a calibration worker, an admin dashboard. I never built the one piece that would let it run.
In thirty-three minutes, MockEvalio went from calling Groq directly from five different services to a centralized orchestrator with versioned prompts and cost-aware multi-provider routing. What built on what, and what's never been touched since.
MockEvalio's single ₹399 plan became three separate prices within nine hours of its first real payment. The change is fully on the record. The reasoning isn't, and I looked.
I built full OpenTelemetry coverage into MockEvalio over one night. By morning, part of what I'd just built was already too loud to keep as-is.
I committed a plan to keep two job-search providers as optional extras. Nineteen minutes later, I committed the opposite. The commit history proves it happened. It doesn't say why.
An LLM that keeps reaching for the same phrasing usually has three separate causes stacked on top of each other. Fixing one rarely fixes the output.
MockEvalio's interview AI kept reaching for the same follow-up phrasing. The fix wasn't one change — it was three, aimed at three different parts of the problem.
Two of MockEvalio's three OAuth logins just logged you in. The third also read your job title and skills out of your headline. Here's the mechanism, and what's still unexplained about the decision.
MockEvalio's resume scorer worked within hours. Turning it into resume intelligence took five more rebuilds in a day and a half — and the record only tells me what changed, not why.
MockEvalio's first RAG pipeline shipped and broke on the same day. What the evidence shows about the failure, the fix, and what the fix didn't prove.
Two hours after MockEvalio's repository existed, a complete application did too. What that actually proves, and what it doesn't.