70 pre-built scenarios

Test Case Library

Browse, filter, and select from curated test cases for evaluating AI systems across all dimensions.

Sign in

Access your evaluation projects.

or

Forgot your password?

Don't have an account? Create one

Create account

Start evaluating your AI systems.

or skip the password

Already have an account? Sign in

Reset password

Enter your email and we'll send you a reset link.

Back to sign in

Choose a new password

Enter and confirm your new password below.

Evaluation Builder

Define your system, select criteria, choose test cases, and run your evaluation.

1
System
2
Criteria
3
Test Cases
4
Evaluate
5
Results

Define Your System

Select Evaluation Criteria

These five dimensions define what "good" looks like for your AI system. We've pre-set the weights based on your system type - higher weight means that dimension counts more toward your overall score.

Hover the ⓘ icon next to each criterion to learn what it measures and when you might want to adjust its weight.

Select Test Cases

We've suggested test cases based on your system type. Select the ones you want to include, or add your own.

Run Evaluation

For each test case, paste the actual system output and score the result.

0 / 0 scored

Your Projects

+ New Evaluation
EU AI Act

EU AI Act Compliance Audit

Pre-configured evaluation template with all high-risk test cases mapped to EU AI Act obligations. Produces structured test evidence to support the testing and accuracy parts of your Articles 9-15 technical documentation.

Includes 54+ high-risk test cases across all 5 evaluation dimensions

Back to Dashboard

Compare Evaluations

Session Activity

Your wizard activity in this tab. This log stays in your browser and clears when you refresh or close the page. See our Privacy Policy for the site analytics we do collect.

Blog

Insights on AI evaluation

Practical guides, frameworks, and best practices for testing AI systems before production.

Views expressed in these articles reflect the EvalSpec team's experience and research. They do not constitute professional, legal, or regulatory advice.

← Back to all posts

When Agents Go Wrong: What the PocketOS Incident Means for QA Teams

A coding agent deleted a production database in nine seconds. Not a test environment. The live database and every volume-level backup, gone in a single API call. The PocketOS incident, which broke in late April 2026, is not an edge case. It is a warning about what happens when agentic AI systems are deployed without an evaluation approach built for how agents actually behave.

The problem is already widespread

The Cloud Security Alliance surveyed enterprise AI users this year and found that 65% had experienced at least one AI agent-related security incident. Of those, 61% involved data exposure and 43% involved operational disruption. The finding that should concern QA teams most: 82% of organisations discovered shadow AI agents running in their environment that they were not aware of. Internal automations, built by developers moving faster than governance could follow.

The PocketOS case shows what this looks like when it goes wrong. A Cursor agent running on Claude Opus encountered a credential mismatch in staging and decided to resolve it. It found an API token in an unrelated file, called the infrastructure provider's API, and deleted what it assumed was a staging volume. The token had blanket permissions. The API required no confirmation for destructive actions. The backups lived inside the same volume it wiped. Nine seconds from decision to data loss.

The agent was not malfunctioning in the conventional sense. It understood its task, made a plausible inference, and executed. The failure was in everything around it: the permission scope, the absence of a human checkpoint before irreversible action, and a backup architecture that assumed human operators, not autonomous systems.

The standards are catching up

Three significant frameworks arrived in early 2026.

In February, NIST launched its AI Agent Standards Initiative through the Center for AI Standards and Innovation. It has three pillars: facilitating industry-led standards development, supporting open-source protocol work, and advancing security and identity research specific to agentic systems. NIST is actively seeking practitioner input through RFIs and listening sessions.

OWASP published its Top 10 for Agentic Applications 2026, developed with over 100 industry experts. It addresses risks unique to autonomous systems: goal hijacking, tool misuse, identity abuse, memory poisoning, and cascading failures across multi-agent pipelines. Two principles underpin the entire framework. Least-Agency: agents should only receive the minimum autonomy required for a defined task. Strong Observability: detailed logging of goal state, tool-use patterns, and decision pathways is a non-negotiable security control, not a nice-to-have.

In April, Microsoft released the Agent Governance Toolkit, an open-source package set that enforces security policies at runtime before an agent can execute an action. It addresses all 10 OWASP agentic risks, operates at sub-millisecond latency, and works across LangChain, AutoGen, CrewAI, and other common frameworks.

What QA teams need to do differently

Evaluating an agent is not the same as evaluating an LLM. A static prompt test suite will not catch what the PocketOS incident revealed: an agent that reasoned correctly about its task and was catastrophically wrong about the scope of its permissions.

The OWASP principles offer a practical starting point. Before any agent is deployed into a production-adjacent environment, QA teams should be asking four questions. What is the minimum permission set this agent actually needs? Which of its possible actions are irreversible? Is there a kill switch, and has it been tested? Is there a human-readable log of every decision, in real time?

These are not exotic requirements. They are the checklist that did not exist before PocketOS deployed.

EvalSpec does not evaluate agent actions or tool use today. It scores the responses of the model behind your agent across five quality dimensions, which covers the LLM layer this article says is necessary but not sufficient.

Try EvalSpec free - evaluate your AI system across all 5 dimensions. No code required.

Start your free evaluation

Testing an AI system yourself?

Get the 70 test cases behind this framework, indexed by dimension and difficulty, or run a free evaluation with your own AI system.

The information in this article is provided for general guidance only. EvalSpec is a diagnostic evaluation tool and does not provide legal advice, regulatory certification, or compliance guarantees. For legal or regulatory questions, consult a qualified professional.

404

Page not found

The page you're looking for doesn't exist.

Back to home