Skill Behavior Testing: Evaluate Contracts, Not Exact Answers
Define observable Agent Skill behavior with MUST, SHOULD, and MUST NOT, then evaluate outcomes, trajectories, artifacts, and side effects instead of fixed wording.
Quality Analyst, Not Quality Assurance.
Articles on software testing, quality analysis, and test engineering: automation testing, API testing, performance testing, UI testing, and AI-assisted testing. Series like "30 Days of AI in Testing Challenge" and "UI Testing Best Practices" share hands-on experience and tooling. Written for testers and developers who care about quality.
Will AI replace testers? Reflections on Rahul Parwal's discussion of AI noise, context engineering, evaluations, testing metrics, tool selection, and the judgment that matters in an AI-era QA career.
Read articleDefine observable Agent Skill behavior with MUST, SHOULD, and MUST NOT, then evaluate outcomes, trajectories, artifacts, and side effects instead of fixed wording.
Combinatorial Testing field guide: select factor levels, pair or t-way coverage, constraints, risks, and evidence.
Pairwise Testing field guide: select factor values, constraints, pair coverage, risk weighting, and uncovered interactions.
Decision Table Testing field guide: model conditions, actions, impossible combinations, priorities, and expected outcomes.
A bilingual guide to deriving traceable state-transition test candidates from states, events, guards, actions, and persistence evidence.
Test Skill routing from discovery to trigger and neighboring capability selection with positive, negative, boundary, and paraphrase cases.
Boundary Value Testing field guide: select lower, upper, adjacent, invalid, and transition values from explicit rules.
Equivalence Partitioning field guide: divide valid, invalid, empty, boundary, and conditional input classes with traceable representatives.
Use L1 through L4 test depth and E1 through E4 evidence levels to choose how far an Agent Skill should be tested.
Edge Case Discovery field guide: explore unusual data, timing, identity, state, environment, and recovery conditions with evidence.
Negative Scenario Discovery field guide: identify rejection, interruption, misuse, invalid state, dependency, and recovery scenarios.