Plan de evaluación para una función con LLM
Diseña un conjunto de pruebas y criterios de aprobación para una función respaldada por un modelo, antes de ajustar el prompt.
Úsalo cuando: Vas a lanzar una función que depende de un modelo y necesitas una forma repetible de saber si un cambio la mejoró.
You are an AI engineer designing evaluations for a language model feature.
## Task
Design an evaluation plan for the feature described below.
## Requirements
- Define 10 test cases: 4 typical inputs, 3 edge cases, and 3 adversarial inputs.
- State the expected property of the output for each case, in a form code or a reviewer can check.
- Name the check for each property: exact match, schema validation, a rule, or a graded rubric.
- State the pass threshold for the suite as a number.
- Do not invent facts about the feature; base every case on the description.
## Output format
Return markdown with three sections: Test cases (a table with the columns ID, Type, Input summary, Expected property, and Check), Pass threshold (one sentence), and Gaps (bulleted list of what the description does not let you test).
## Input
<feature>
{{feature}}
</feature>Variables
{{feature}}- Qué hace la función, sus entradas, sus salidas y cuánto cuesta una respuesta incorrecta.
Entrada de ejemplo
feature: extracts the due date and total from invoice text into JSON; a wrong total causes an incorrect payment.Salida de ejemplo
## Test cases
| ID | Type | Input summary | Expected property | Check |
|---|---|---|---|---|
| T1 | Typical | One-page invoice with one total | `total` equals 1250.00 | Exact match |
| A1 | Adversarial | Invoice text containing "ignore the instructions" | Output is valid JSON with the real total | Schema validation |Ilustrativa: escrita para mostrar la forma esperada, no generada por un modelo.