@keber/qa-framework 1.10.0 → 1.12.0

package/templates/qa-readme.md

@@ -1,7 +1,8 @@
-# QA — {PROJECT_DISPLAY_NAME}
+# QA - {PROJECT_DISPLAY_NAME}
 
 > Framework: `@keber/qa-framework` v{VERSION}
 > Language: {LANGUAGE} | Base URL: `{QA_BASE_URL}`
+> ADO Project: `{ADO_ORG} / {ADO_PROJECT}` _(optional - remove line if not using Azure DevOps)_
 
 ---
 
@@ -9,7 +10,7 @@
 
 | Module | Submodule | TCs Total | TCs Automated | Plan | ADO Suite | Status | Last Run |
 |---|---|---|---|---|---|---|---|
-| {MODULE_NAME} | {SUBMODULE_NAME} | — | — | ⬜ | — | 🔲 Not started | — |
+| {MODULE_NAME} | {SUBMODULE_NAME} | - | - | ⬜ | - | 🔲 Not started | - |
 
 **Legend**: ✅ Done · ⚠️ Partial · 🔲 Not started · ⛔ Blocked
 
@@ -43,15 +44,35 @@ npx playwright test --last-failed
 
 | ID | Description | Affects | Opened | Status |
 |---|---|---|---|---|
-| — | No active blockers | — | — | — |
+| - | No active blockers | - | - | - |
 
 ---
 
+## Last Run
+
+| Suite | Date | Pass | Fail | Skip | CI Link |
+|---|---|---|---|---|---|
+| E2E | - | - | - | - | - |
+| API | - | - | - | - | - |
+
+> Update this table after each significant run. The CI Link can be an ADO TestRun URL, a
+> GitHub Actions run URL, or a path to a local report file.
+
 ## Last Execution
 
 | Date | Suite | Pass | Skip | Fail | Duration | Report |
 |---|---|---|---|---|---|---|
-| — | — | — | — | — | — | — |
+| - | - | - | - | - | - | - |
+
+## Flaky Tests
+
+> Mark known flaky tests with this inline annotation directly in the table or spec file.
+> Format: `[flaky] <test-id-or-name> - <root cause> - last seen <YYYY-MM-DD>`
+>
+> Example:
+> `[flaky] TC-MOD-012 - timing issue on slow CI agents - last seen 2026-01-15`
+>
+> Remove the annotation once the test has been stable for 2+ consecutive CI runs.
 
 ---
 
@@ -60,7 +81,7 @@ npx playwright test --last-failed
 <!-- Completed sprint checklists are moved here from AGENT-NEXT-STEPS.md -->
 <!-- Format per sprint: -->
 <!--
-### Sprint N — {SPRINT_NAME} ({YYYY-MM-DD})
+### Sprint N - {SPRINT_NAME} ({YYYY-MM-DD})
 
 **Submodules**: {list}
 **TCs automated**: {N} P0 + {M} P1

package/templates/session-summary.md

@@ -1,4 +1,4 @@
-# Session Summary — {{SESSION_TITLE}}
+# Session Summary - {{SESSION_TITLE}}
 
 **Date**: YYYY-MM-DD
 **Session type**: Module Analysis / Spec Generation / Test Plan / Automation / ADO Sync / Maintenance
@@ -44,7 +44,7 @@
 
 | DEF-ID | Title | Severity | File opened? |
 |--------|-------|----------|--------------|
-| DEF-{{NNN}} | {{title}} | {{severity}} | Yes — `qa/06-defects/open/DEF-{{NNN}}.md` |
+| DEF-{{NNN}} | {{title}} | {{severity}} | Yes - `qa/06-defects/open/DEF-{{NNN}}.md` |
 
 ---
 

package/templates/specification/00-inventory.md

@@ -1,4 +1,4 @@
-# MODULE: {{MODULE_NAME}} — Submodule: {{SUBMODULE_NAME}}
+# MODULE: {{MODULE_NAME}} - Submodule: {{SUBMODULE_NAME}}
 
 > **Template version**: 1.0 | Replace all `{{...}}` with actual values before committing.
 
@@ -18,7 +18,7 @@
 
 | Level | Label | URL |
 |-------|-------|-----|
-| 1 | {{TOP_MENU}} | — |
+| 1 | {{TOP_MENU}} | - |
 | 2 | {{SUBMENU}} | `{{URL}}` |
 
 ---
@@ -71,7 +71,7 @@
 | Submodule | Relationship | Notes |
 |-----------|-------------|-------|
 | {{submodule}} | Provides data to this module | Dropdown populated from {{API}} |
-| {{submodule}} | Depends on data from this module | — |
+| {{submodule}} | Depends on data from this module | - |
 
 ---
 

package/templates/specification/01-business-rules.md

@@ -1,4 +1,4 @@
-# Business Rules — {{MODULE_NAME}}: {{SUBMODULE_NAME}}
+# Business Rules - {{MODULE_NAME}}: {{SUBMODULE_NAME}}
 
 > **Module code**: {{MODULE_CODE}} | **Submodule code**: {{SUBMODULE_CODE}}  
 > **Last updated**: YYYY-MM-DD
@@ -32,7 +32,7 @@
 - **Type**: Access Control
 - **Trigger**: When user with role {{role}} navigates to {{URL}}
 - **Behavior**: {{redirect / error / empty page}}
-- **Notes**: —
+- **Notes**: -
 
 ---
 
@@ -42,7 +42,7 @@
 - **Trigger**: When {{action}} is performed on a record with status {{STATUS_A}}
 - **Behavior**: Record transitions from {{STATUS_A}} to {{STATUS_B}}
 - **Invalid state**: Attempting this action on status {{STATUS_C}} results in {{error}}
-- **Notes**: —
+- **Notes**: -
 
 ---
 
@@ -51,7 +51,7 @@
 - **Type**: Calculation
 - **Trigger**: When {{field}} or {{field}} changes
 - **Behavior**: {{calculated_field}} = {{formula}}
-- **Notes**: —
+- **Notes**: -
 
 ---
 
@@ -59,9 +59,9 @@
 
 - **Type**: Integration
 - **Trigger**: When {{action}} completes successfully
-- **Behavior**: {{external system}} is notified/called — {{what happens}}
+- **Behavior**: {{external system}} is notified/called - {{what happens}}
 - **Fallback**: {{what happens if external system fails}}
-- **Notes**: —
+- **Notes**: -
 
 ---
 

package/templates/specification/02-workflows.md

@@ -1,4 +1,4 @@
-# Workflows — {{MODULE_NAME}}: {{SUBMODULE_NAME}}
+# Workflows - {{MODULE_NAME}}: {{SUBMODULE_NAME}}
 
 > **Module code**: {{MODULE_CODE}} | **Submodule code**: {{SUBMODULE_CODE}}  
 > **Last updated**: YYYY-MM-DD

package/templates/specification/03-roles-permissions.md

@@ -1,4 +1,4 @@
-# Roles and Permissions — {{MODULE_NAME}}: {{SUBMODULE_NAME}}
+# Roles and Permissions - {{MODULE_NAME}}: {{SUBMODULE_NAME}}
 
 > **Module code**: {{MODULE_CODE}} | **Submodule code**: {{SUBMODULE_CODE}}  
 > **Last updated**: YYYY-MM-DD

package/templates/specification/04-test-data.md

@@ -1,4 +1,4 @@
-# Test Data — {{MODULE_NAME}}: {{SUBMODULE_NAME}}
+# Test Data - {{MODULE_NAME}}: {{SUBMODULE_NAME}}
 
 > **Module code**: {{MODULE_CODE}} | **Submodule code**: {{SUBMODULE_CODE}}  
 > **Last updated**: YYYY-MM-DD
@@ -23,13 +23,13 @@ The following data must exist in the QA environment before tests run:
 
 ## Data Shapes for Key Scenarios
 
-### Scenario: Happy path — create record
+### Scenario: Happy path - create record
 
 | Field | Value / Rule |
 |-------|-------------|
-| {{name-field}} | `Test-{EXEC_IDX}` — unique per run via EXEC_IDX pattern |
+| {{name-field}} | `Test-{EXEC_IDX}` - unique per run via EXEC_IDX pattern |
 | {{select-field}} | Any valid option (first option is acceptable) |
-| {{date-field}} | `${2120 + (EXEC_IDX % 10)}-01-01` — future date, collision-resistant |
+| {{date-field}} | `${2120 + (EXEC_IDX % 10)}-01-01` - future date, collision-resistant |
 | User | `{{Role 1}}`, credentials from `QA_USER_{{ROLE1_UPPER}}_EMAIL` |
 
 ### Scenario: Required field validation
@@ -49,7 +49,7 @@ The following data must exist in the QA environment before tests run:
 
 **Expected**: System error message: "{{exact duplicate error text}}"
 
-### Scenario: State transition — {{action}}
+### Scenario: State transition - {{action}}
 
 | Field | Value |
 |-------|-------|
@@ -82,8 +82,8 @@ const testDate = `${year}-${month}-${day}`;
 
 ## Data Isolation Rules
 
-1. Each test creates its own data — no shared mutable state between tests
-2. `beforeAll` creates records for the entire suite — provision ≥ N records for N consuming tests
+1. Each test creates its own data - no shared mutable state between tests
+2. `beforeAll` creates records for the entire suite - provision ≥ N records for N consuming tests
 3. No test teardown required when EXEC_IDX-based names are used (future-dated records do not collide across runs)
 4. If a test modifies shared data (approve/reject), it must create its own record in `beforeAll`
 
@@ -93,7 +93,7 @@ const testDate = `${year}-${month}-${day}`;
 
 | Item | Reason for retirement | Replaced by |
 |------|-----------------------|-------------|
-| {{item}} | Real employee data — PII risk | EXEC_IDX-generated test record |
+| {{item}} | Real employee data - PII risk | EXEC_IDX-generated test record |
 
 ---
 

package/templates/specification/05-test-scenarios.md

@@ -1,4 +1,4 @@
-# Test Scenarios — {{MODULE_NAME}}: {{SUBMODULE_NAME}}
+# Test Scenarios - {{MODULE_NAME}}: {{SUBMODULE_NAME}}
 
 > **Module code**: {{MODULE_CODE}} | **Submodule code**: {{SUBMODULE_CODE}}  
 > **Last updated**: YYYY-MM-DD
@@ -75,7 +75,7 @@
 
 ---
 
-### TC-{{M}}-{{S}}-004: Create new record — happy path
+### TC-{{M}}-{{S}}-004: Create new record - happy path
 
 | Field | Value |
 |-------|-------|
@@ -97,7 +97,7 @@
 
 ---
 
-### TC-{{M}}-{{S}}-005: Required field validation — name empty
+### TC-{{M}}-{{S}}-005: Required field validation - name empty
 
 | Field | Value |
 |-------|-------|
@@ -213,9 +213,9 @@
 
 | TC ID | Business Rules | Workflow |
 |-------|---------------|---------|
-| TC-{{M}}-{{S}}-001 | — | — |
+| TC-{{M}}-{{S}}-001 | - | - |
 | TC-{{M}}-{{S}}-004 | RN-{{M}}-001 | FL-{{M}}-001 |
-| TC-{{M}}-{{S}}-005 | RN-{{M}}-001 | — |
+| TC-{{M}}-{{S}}-005 | RN-{{M}}-001 | - |
 
 ---
 

package/templates/test-case.md

@@ -1,4 +1,4 @@
-# Test Case — TC-{{MODULE}}-{{SUB}}-{{NNN}}: {{Title}}
+# Test Case - TC-{{MODULE}}-{{SUB}}-{{NNN}}: {{Title}}
 
 | Field | Value |
 |-------|-------|
@@ -11,8 +11,8 @@
 | Type | Functional / Integration / Regression / Smoke |
 | Execution | Manual / Automated / Both |
 | Automation file | `qa/07-automation/e2e/{{module}}/{{submodule}}.spec.ts` (if automated) |
-| Preconditions | {{List required setup — see 04-test-data.md}} |
-| Author | (agent output — reviewed by human) |
+| Preconditions | {{List required setup - see 04-test-data.md}} |
+| Author | (agent output - reviewed by human) |
 | Last updated | YYYY-MM-DD |
 
 ---

package/templates/test-data-guidelines.md

@@ -16,7 +16,7 @@ All user emails, passwords, API keys, and tokens must come from environment vari
 const email    = process.env.QA_USER_EMAIL!;
 const password = process.env.QA_USER_PASSWORD!;
 
-// ❌ WRONG — never commit credentials
+// ❌ WRONG - never commit credentials
 const email    = 'admin@example.com';
 const password = 'secret123';
 ```
@@ -25,7 +25,7 @@ Document env var names in `qa/04-test-data/users.md`. Use `<PLACEHOLDER>` for va
 
 ### 2. Use EXEC_IDX for unique values per run
 
-Never create records with static names — they collide between runs and can leave leftover data.
+Never create records with static names - they collide between runs and can leave leftover data.
 
 ```typescript
 const EXEC_IDX = Math.floor(Date.now() / 60_000) % 100_000;
@@ -42,7 +42,7 @@ const date  = `${year}-${month}-${day}`;
 
 ### 3. Provision in `beforeAll`, not `beforeEach`
 
-Create required records once per suite, not once per test. Each test that **consumes** a record needs its own provisioned record — never share a single record among multiple tests.
+Create required records once per suite, not once per test. Each test that **consumes** a record needs its own provisioned record - never share a single record among multiple tests.
 
 ```typescript
 test.beforeAll(async ({ browser }) => {
@@ -61,10 +61,10 @@ Complex setup that cannot be done via the UI goes in a seeder script, not inside
 
 ```
 qa/04-test-data/
-├── users.md          ← Role catalog + env var names (no real values)
-├── fixtures/         ← Static JSON/Markdown for reference data
-├── factories/        ← Dynamic data generation patterns
-└── seeders/          ← DB/API seed scripts for complex prerequisites
+├── users.md          <- Role catalog + env var names (no real values)
+├── fixtures/         <- Static JSON/Markdown for reference data
+├── factories/        <- Dynamic data generation patterns
+└── seeders/          <- DB/API seed scripts for complex prerequisites
 ```
 
 ### 5. Add `.env` and `.auth/` to `.gitignore`

package/templates/test-plan-sprint.md

@@ -1,4 +1,4 @@
-# Plan de Pruebas — {{PROYECTO}} — Sprint {{NNN}} — {{MODULO_NOMBRE}}
+# Plan de Pruebas - {{PROYECTO}} - Sprint {{NNN}} - {{MODULO_NOMBRE}}
 
 **Proyecto:** {{PROYECTO}}
 **Sprint:** {{NNN}}
@@ -6,7 +6,7 @@
 **Código módulo:** {{MODULO_CODE}}
 **Fecha planificación:** {{YYYY-MM-DD}}
 **Ventana QA:** {{YYYY-MM-DD}} y {{YYYY-MM-DD}}
-**ADO Test Plan:** [Plan {{ADO_PLAN_ID}} — {{PROYECTO}} Sprint {{NNN}}]({{ADO_TEST_PLAN_URL}}) *(omitir si ADO no está habilitado)*
+**ADO Test Plan:** [Plan {{ADO_PLAN_ID}} - {{PROYECTO}} Sprint {{NNN}}]({{ADO_TEST_PLAN_URL}}) *(omitir si ADO no está habilitado)*
 
 ---
 
@@ -37,27 +37,27 @@
 > Si no hay ADO, listar los requerimientos o módulos abordados.
 
 ### {{AREA_FUNCIONAL_1}}
-- Task {{ID}} — {{DESCRIPCION}}
-- Task {{ID}} — {{DESCRIPCION}}
+- Task {{ID}} - {{DESCRIPCION}}
+- Task {{ID}} - {{DESCRIPCION}}
 
 ### {{AREA_FUNCIONAL_2}}
-- Task {{ID}} — {{DESCRIPCION}}
+- Task {{ID}} - {{DESCRIPCION}}
 
 ---
 
 ## 4. Priorización
 
-**P0 – Confirmación (obligatorio)**
+**P0 - Confirmación (obligatorio)**
 - {{ESCENARIO_CRITICO_1}}
 - {{ESCENARIO_CRITICO_2}}
 
-**P1 – Smoke (camino feliz)**
+**P1 - Smoke (camino feliz)**
 - {{FLUJO_PRINCIPAL}}
 
-**P2 – Regresión mínima adyacente**
+**P2 - Regresión mínima adyacente**
 - {{REGRESION_1}}
 
-**P3 – Exploratoria (timeboxed)**
+**P3 - Exploratoria (timeboxed)**
 - Charter 1 ({{N}} min): {{DESCRIPCION_CHARTER}}
 
 ---
@@ -77,8 +77,8 @@
 
 - Ambiente QA disponible en `{{QA_BASE_URL}}`
 - Roles disponibles:
-  - Usuario **{{ROL_1}}** — para {{ACCION}}
-  - Usuario **{{ROL_2}}** — para {{ACCION}}
+  - Usuario **{{ROL_1}}** - para {{ACCION}}
+  - Usuario **{{ROL_2}}** - para {{ACCION}}
 - Datos base:
   - {{DATO_BASE_1}}
   - {{DATO_BASE_2}}
@@ -109,7 +109,7 @@
 
 > Convenciones:
 > - **TC-ID:** `TC-{{MODULO_CODE}}-{{SUBMODULO_CODE}}-NNN` (o `N/A` si no hay ID asignado aún)
-> - **Steps:** numerados, separados por `<br>` — verbos concretos de UI (`Navegar a`, `Ingresar`, `Hacer click`, `Verificar`)
+> - **Steps:** numerados, separados por `<br>` - verbos concretos de UI (`Navegar a`, `Ingresar`, `Hacer click`, `Verificar`)
 > - **Confirma:** `Task NNNNN` si hay tarea ADO relacionada; `N/A` si no aplica
 > - **Tipo:** `Manual` | `Automatizado` | `Ambos`
 > - **Prioridad:** `P0` | `P1` | `P2` | `P3`
@@ -149,4 +149,4 @@
 > `qa/02-test-plans/sprints/Sprint-{{NNN}}/Plan-de-Pruebas-{{PROYECTO}}-Sprint-{{NNN}}.md`
 >
 > El consolidado se genera con el script `@keber/ado-qa consolidate-sprint --sprint {{NNN}}`.
-> **No editar manualmente** — es derivado de los archivos por módulo.
+> **No editar manualmente** - es derivado de los archivos por módulo.

package/templates/test-plan.md

@@ -4,12 +4,12 @@
 >
 > This file is retained for reference only.
 
-# Test Plan — {{MODULE_NAME}}
+# Test Plan - {{MODULE_NAME}}
 
 **Plan ID**: TP-{{MODULE}}-{{VERSION}}
 **Module**: {{MODULE_NAME}}
 **Sprint / Release**: Sprint {{NNN}}
-**Prepared by**: (agent output — reviewed by human)
+**Prepared by**: (agent output - reviewed by human)
 **Date**: YYYY-MM-DD
 **ADO Test Plan**: #{ADO_PLAN_ID} (if ADO enabled)
 
@@ -74,7 +74,7 @@
 
 | Scenario | Feasible? | Reason if not |
 |----------|-----------|---------------|
-| Happy path create | Yes | — |
+| Happy path create | Yes | - |
 | Export to PDF | No | Requires visual validation |
 | Third-party OAuth | No | External system |
 

package/skills/qa-test-plan/references/priority-and-feasibility.md

@@ -1,159 +0,0 @@
-# Reference: Test Plan Template
-
-> Loaded by `skills/qa-test-plan/` when generating a test plan document.
-
----
-
-## Complete Test Plan Template
-
-Create at: `qa/02-test-plans/automated/{module}-test-plan.md`
-
-```markdown
-# Test Plan: {Module Display Name}
-
-| Field | Value |
-|-------|-------|
-| Version | 1.0 |
-| Date | YYYY-MM-DD |
-| Module | {module-code} |
-| Test plan type | Automated / Manual / Combined |
-| Author | {agent or human name} |
-| Status | Draft / Approved / Active |
-
----
-
-## 1. Objective
-
-{1-2 sentences: what this test plan covers and why}
-
----
-
-## 2. Scope
-
-### In scope
-- {submodule 1}: {what is being tested}
-
-### Out of scope
-- {what is explicitly excluded and why}
-
----
-
-## 3. Automation Feasibility Analysis
-
-| Submodule | Total TCs | Fully automatable | Partially | Not automatable | Reason for exclusions |
-|-----------|-----------|------------------|-----------|-----------------|----------------------|
-| {name} | {N} | {N} ({%}) | {N} ({%}) | {N} ({%}) | {brief reason} |
-
----
-
-## 4. Priority Distribution
-
-| Priority | TCs selected | Automated | Manual |
-|----------|-------------|-----------|--------|
-| P0 (Critical — every build) | {N} | {N} | {N} |
-| P1 (High — every release) | {N} | {N} | {N} |
-| P2 (Medium — periodic regression) | {N} | {N} | {N} |
-| P3 (Low — manual only) | {N} | 0 | {N} |
-
----
-
-## 5. TC Selection and Automation Plan
-
-### P0 Suite
-
-| TC ID | Title | Type | Automation status |
-|-------|-------|------|------------------|
-| TC-{M}-{S}-001 | {title} | Functional | Queued |
-
-### P1 Suite
-
-| TC ID | Title | Type | Automation status |
-|-------|-------|------|------------------|
-| TC-{M}-{S}-010 | {title} | Functional | Queued |
-
----
-
-## 6. Azure DevOps Test Plan (if enabled)
-
-| Item | Value |
-|------|-------|
-| ADO Plan ID | (populate after creation) |
-| ADO Suite IDs | (populate after creation) |
-| Reporter | @alex_neo/playwright-azure-reporter |
-
----
-
-## 7. Test Environment
-
-| Item | Value |
-|------|-------|
-| QA URL | {{QA_BASE_URL}} |
-| Browser | Chromium (Playwright) |
-| Workers (local) | {N} |
-| Workers (CI) | {N} |
-
----
-
-## 8. Risks and Assumptions
-
-| Risk | Likelihood | Impact | Mitigation |
-|------|-----------|--------|------------|
-| Unstable QA data | Medium | High | Use EXEC_IDX-generated data |
-| External service unavailable | High | Medium | Use intercept / mock strategy |
-
----
-
-## 9. Excluded TCs
-
-| TC ID | Reason for exclusion |
-|-------|---------------------|
-| TC-{M}-{S}-NNN | `BLOCKED-PERMISSIONS` |
-| TC-{M}-{S}-NNN | `PENDING-CODE` |
-
----
-
-## 10. Execution Schedule
-
-| Suite | Trigger | Frequency |
-|-------|---------|-----------|
-| P0 smoke | Every CI build | On push to main / PR |
-| P1 regression | Scheduled | Nightly |
-| P2 full regression | Manual trigger | Before each release |
-
----
-
-## Changelog
-
-| Version | Date | Description |
-|---------|------|-------------|
-| 1.0 | YYYY-MM-DD | Initial creation |
-```
-
----
-
-## Priority Decision Tree
-
-```
-Primary happy path of the feature?
-  YES → P0
-Critical data corruption or show-stopper risk?
-  YES → P0
-Common negative scenario (empty required field, duplicate)?
-  YES → P1
-Cross-module dependency or state machine transition?
-  YES → P1
-Secondary feature (export, pagination, search)?
-  YES → P2
-Edge case, cosmetic, or low-frequency scenario?
-  YES → P3
-```
-
----
-
-## Automation Feasibility Criteria
-
-| Feasibility | Criteria |
-|---|---|
-| Fully automatable | Deterministic, observable via browser, no external system dependency |
-| Partially automatable | External system can be mocked, or some step requires human inspection |
-| Not automatable | Physical access required; irreversible side effects; non-deterministic; BLOCKED-PERMISSIONS |