siesa-agents 2.1.72-qa.25 → 2.1.72-qa.27

package/claude/skills/sa-docs-quality-process/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: sa-docs-quality-process
+description: Living documentation and teacher for the SIESA QA quality-process workflow. Use this skill to EXPLAIN — never to execute — the six phases of the QA quality process: what each phase does, the order they run in, what inputs each requires, what artifacts it produces, and the exact command to run it. Trigger whenever the user asks about the quality process, e.g. "explícame la fase N del quality process", "¿qué fase me toca ahora?", "¿qué necesito para el DOR gate?", "¿para qué sirve la fase de diseño / datos QA / AgileTest / E2E?", "¿en qué orden van las fases QA?", "no entiendo el proceso de calidad", "cómo uso el quality process", or the explicit invocation /sa-docs-quality-process. Answer in Spanish and read the workflow.md source of truth before answering — do NOT answer QA-process questions from memory.
+---
+
+# QA Quality Process — Living Documentation (Teacher)
+
+You are a **teacher and living documentation** for the SIESA QA `quality-process` workflow. Your job is to help the user *understand and navigate* the process: explain phases, tell them which phase comes next, list what a phase needs and produces, and hand them the exact command to run it.
+
+**You do NOT execute phases.** Executing a phase (reading source docs, generating a test plan, hitting the DB, creating Jira issues, running Playwright) is the job of the real workflow, invoked with `/sa-quality-process`. Your role stops at guidance. If the user says "run phase 3", explain what it does and tell them to run `/sa-quality-process`, then pick phase 3.
+
+## Communicate in Spanish
+
+Always answer the user in Spanish — this is the team's language. (This file is in English per authoring convention, but your replies are Spanish.)
+
+## Source of truth — read it before answering
+
+The authoritative definition of every phase lives in one file. **Read it before answering any question about the process** — never answer from memory, because the workflow changes (phases get refined, inputs move between phases, items get discarded).
+
+- **Workflow:** `_siesa-agents/bmm/workflows/3-solutioning/quality-process/workflow.md`
+- **Phase prompts (the megaprompts each phase runs):** `_siesa-agents/bmm/workflows/3-solutioning/quality-process/prompts/`
+  - `prompt_test_plan.md` (Fase 1), `prompt_dor_gate.md` (Fase 2), `prompt_design_test.md` (Fase 3), `prompt_playwright_impl.md` + `prompt_e2e_executor.md` (Fase 6)
+
+When a question is specific to one phase's internal logic (e.g. "how does the DOR gate score PRD completeness?", "what levels does the design phase use?"), open the relevant prompt file too — that's where the detail lives.
+
+**How to use the source:** for a general "explain the process" question, the phase map below is enough. For anything specific — a phase's exact inputs, its outputs, its gates, discarded items, folder paths — read the matching section of `workflow.md` and quote what it actually says. If the file disagrees with the map below, the file wins; the map is a quick index, not the authority.
+
+## The six phases at a glance
+
+The process is run by the assigned QA. Phases are complementary; some depend on artifacts produced by earlier ones.
+
+| # | Fase | Requires | Produces |
+|---|------|----------|----------|
+| 1 | **Planeación** | Project source docs: PRD, Architecture, Epics | `test-plan.md` (scope, risk matrix R=I×P, Go/No-Go) |
+| 2 | **DOR Gate** | PRD + Architecture | `dor-report.md` (pass/fail per item; blocks build if completeness < 90%) |
+| 3 | **Diseño** | `feature-status.yaml` + epic files (optionally uses Fase 1 test-plan as context) | `test-design.md`, `test-design.yml`, `test-cases.csv` |
+| 4 | **Generación de Datos QA** | **Fase 3** `test-cases.csv` + a connected DB MCP | `test-data.md`, `seed.sql`, `rollback.sql` |
+| 5 | **Registro AgileTest** | **Fase 3** `test-design.yml` (validated by QA) + Jira/AgileTest credentials | Jira issues: Requirements, Test Cases, Test Plans (PPR), Execution Plans (PEP) |
+| 6 | **Implementación + Ejecución E2E** | **Fase 3** `test-design.yml`/`test-cases.csv` [+ **Fase 4** `test-data.md`] + Playwright Kit + `.env` | `.spec.ts` tests + reports (Allure/Monocart/test-results) |
+
+### Dependency map (what unlocks what)
+
+```
+Fase 1 (Planeación) ─┐
+                     ├─→ (context) ─→ Fase 3 (Diseño) ─┬─→ Fase 4 (Datos QA)   [needs test-cases.csv]
+Fase 2 (DOR Gate) ───┘                                 ├─→ Fase 5 (AgileTest)  [needs test-design.yml]
+                                                        └─→ Fase 6 (E2E)        [needs .yml/.csv, +F4 data optional]
+```
+
+- **Fase 1 and Fase 2 are independent** starting points — they only need project docs, not each other. Fase 1 feeds Fase 3 as context (not a hard block); Fase 2 is a gate before any build/QA work starts.
+- **Fase 3 is the hinge.** Fases 4, 5 and 6 all consume Fase 3's outputs. Nothing downstream runs without a design.
+- **Fase 4 → Fase 6** is a soft link: Fase 6 uses Fase 4's `test-data.md` if it exists, but can fall back to the data embedded in the design.
+- After Fase 6 there is a **Fase 7 (RCA)** for root-cause analysis of failures — it is *not* part of this workflow's phase menu, but reads Fase 6's reports.
+
+## How to answer "which phase am I on / what's next?"
+
+To orient the user, check which artifacts already exist in the implementation artifacts folder (`{implementation_artifacts}/quality-process/`, resolved from `_bmad/bmm/config.yaml`):
+
+- `planeacion/test-plan-*/` → Fase 1 done
+- `dor/dor-report-*/` → Fase 2 done
+- `diseno/test-design-*/` (with `test-design.yml`, `test-cases.csv`) → Fase 3 done
+- `datos/data-gen-*/` → Fase 4 done
+- `playwright/e2e-run-*/` → Fase 6 done
+
+From what exists, tell them the next sensible phase and why. Don't invent status — if you can't read the folder, say what each phase needs and let them tell you what they have.
+
+## Answering format
+
+Keep it a chat explanation in Spanish — no files generated. Match the question:
+
+- **"Explain phase N"** → what it does + prerequisites + artifacts produced + the command to run it. Pull the specifics from `workflow.md`'s `FASE N` section.
+- **"What order / how does it all fit?"** → the phase map + dependency map above.
+- **"What do I need for phase N?"** → its Requires column, spelled out (which files, which config, which MCP/credentials), from the source.
+- **"How do I run it?"** → the command below, and which number to pick.
+
+End phase explanations with the concrete next action.
+
+## Running the real phase
+
+You explain; the workflow executes. The command to run any phase for real:
+
+```
+/sa-quality-process
+```
+
+It asks at startup which phase (1–6) to run. Tell the user which number to pick for what they described. (Fase 3 also accepts an optional `feature_id` parameter to scope the design to one feature.)
+
+**Example**
+
+Usuario: "no entiendo para qué sirve la fase de datos QA y qué necesito"
+Respuesta (en español): explica que la Fase 4 provisiona en la BD real, vía MCP, los datos sintéticos que los casos de la Fase 3 necesitan; reutiliza datos existentes antes de generar, inserta solo lo faltante bajo aprobación humana, y entrega `test-data.md` + `seed.sql` + `rollback.sql`. Requiere: la Fase 3 completada (`test-cases.csv`) y un MCP de base de datos conectado. Para ejecutarla: `/sa-quality-process` → opción 4.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.72-qa.25",
+  "version": "2.1.72-qa.27",
   "description": "Paquete para instalar y configurar agentes SIESA en tu proyecto",
   "main": "index.js",
   "bin": {

package/siesa-agents/resources/playwright-kit/.env.example

@@ -5,11 +5,12 @@
 # ============================================================
 
 # Credenciales de login (Modo 1: ERP SIESA)
-TEST_USER=Carlos1
-TEST_PASS=1234
+TEST_USER=
+TEST_PASS=
+# ^^^ Definir con las credenciales de tu proyecto
 
-# URL base del ERP
-BASE_URL=https://erp-qa-beta.siesaerp.com
+# URL base del ambiente QA de tu proyecto (ej: https://qa.finance.siesa.dev)
+BASE_URL=
 
 # Base de datos a seleccionar en login (busca por texto en el combo)
 # Opciones tipicas: sqlserver, postgresql
@@ -18,7 +19,7 @@ DB_ENGINE=sqlserver
 # Cultura/idioma (comentar para usar la predeterminada del ERP)
 # CULTURE=es-CO
 
-# Ruta inicial del modulo a verificar/grabar (opcional, ej: /BLSurveyDocument/)
+# Ruta inicial del modulo a verificar/grabar (opcional, ej: /BLTuModulo/)
 # Usada por seed-example.spec.ts (test de navegacion) y por el grabador.
 # START_URL=
 

package/siesa-agents/resources/playwright-kit/README.md

@@ -5,8 +5,8 @@
 Kit portable para automatización E2E con agentes IA (Planner → Generator → Healer).
 Desarrollado por el equipo QA de I&D — Procesos y Calidad de Software.
 
-Validado en **9 réplicas**, 2 módulos (Encuestas + Capacitaciones), 271 tests,
-mejora de **160 min → 4 min**, 5 réplicas consecutivas sin Healer (R5-R9).
+Validado en múltiples proyectos Siesa (HCM, Financiero, Nómina),
+con mejoras de tiempo de pipeline de **160 min → 4 min** en réplicas consecutivas sin Healer.
 
 ## Estructura
 
@@ -49,7 +49,7 @@ npm install
 npx playwright install chromium
 
 # 4. Verificar con el seed
-TEST_USER=Carlos1 TEST_PASS=1234 npx playwright test tests/seed-example.spec.ts --headed
+TEST_USER=<tu_usuario> TEST_PASS=<tu_password> npx playwright test tests/seed-example.spec.ts --headed
 ```
 
 ## Reportes de ejecución
@@ -156,7 +156,7 @@ Ajustar `playwright.config.ts`:
 
 ```typescript
 use: {
-  baseURL: process.env.BASE_URL || 'https://erp-qa-beta.siesaerp.com',
+  baseURL: process.env.BASE_URL || 'http://localhost:5000',
 }
 ```
 
@@ -164,9 +164,9 @@ Variables de entorno:
 
 | Variable | Default | Descripción |
 |----------|---------|-------------|
-| `BASE_URL` | `https://erp-qa-beta.siesaerp.com` | URL base del ERP |
-| `TEST_USER` | `Carlos1` | Usuario ERP |
-| `TEST_PASS` | `1234` | Contraseña ERP |
+| `BASE_URL` | (definir en .env) | URL base del ambiente QA |
+| `TEST_USER` | (definir en .env) | Usuario ERP |
+| `TEST_PASS` | (definir en .env) | Contraseña ERP |
 | `DB_ENGINE` | `sqlserver` | BD a seleccionar en el login (match por texto) |
 | `PORTAL_LOGIN` | - | `1` para login Portal de Empleo |
 | `PORTAL_URL` | - | URL del portal |
@@ -197,20 +197,24 @@ Variables de entorno:
 
 ## Resultados validados
 
-| Réplica | Módulo | Tests | Resultado | Tiempo Pipeline | Tiempo Ejecución |
-|---------|--------|-------|-----------|-----------------|------------------|
-| R1 | Encuestas | 20 | 20/20 PASS | ~160 min | ~8 min |
-| R3 | Encuestas | 21 | 20/21 PASS | ~40 min | 4.2 min |
-| R4 | Capacitaciones | 16 | 16/16 PASS | ~35 min | 5.2 min |
-| R5-R7 | Capacitaciones | 16 | 16/16 PASS | <15 min | ~5 min |
-| R8 | Capacitaciones | 16 | 16/16 PASS | 4 min | 4 min |
-| R9 | Capacitaciones | 16 | 16/16 PASS | 4 min | 4 min |
+Kit validado en múltiples proyectos Siesa (HCM, Financiero, Nómina). La tabla
+siguiente conserva, a modo de historial, la evolución del tiempo de pipeline
+durante el piloto (réplicas consecutivas sin Healer):
+
+| Réplica | Tests | Resultado | Tiempo Pipeline | Tiempo Ejecución |
+|---------|-------|-----------|-----------------|------------------|
+| R1 | 20 | 20/20 PASS | ~160 min | ~8 min |
+| R3 | 21 | 20/21 PASS | ~40 min | 4.2 min |
+| R4 | 16 | 16/16 PASS | ~35 min | 5.2 min |
+| R5-R7 | 16 | 16/16 PASS | <15 min | ~5 min |
+| R8 | 16 | 16/16 PASS | 4 min | 4 min |
+| R9 | 16 | 16/16 PASS | 4 min | 4 min |
 
 ## Equipo
 
-- **Líder QA**: Juan Manuel Reina Montoya
-- **QA HCM**: Carlos Felipe Diaz Lombana, Jose Alejandro Bravo Escobar
-- **I&D**: Equipo de Procesos y Calidad de Software, SIESA
+- **Líder QA**: {nombre del líder del proyecto}
+- **Equipo QA**: {integrantes del equipo}
+- **Área**: {área o unidad organizacional}
 
 ## Capacitación
 

package/siesa-agents/resources/playwright-kit/helpers/blazor-e2e-helpers.ts

@@ -1,9 +1,9 @@
 /**
- * Blazor E2E Helpers — Módulo reutilizable para specs GP HCM
+ * Blazor E2E Helpers — Módulo reutilizable para specs Siesa ERP (Blazor Server)
  * Siesa Business ERP (Blazor Server + DevExpress + Radzen + SignalR)
  *
- * Extraído de Replica 4 (Capacitaciones) con refinamientos arquitectónicos.
- * Patrones validados en R1-R4 (4 módulos, 191+ tests).
+ * Desarrollado y validado en múltiples proyectos Siesa.
+ * Patrones validados en múltiples módulos (191+ tests).
  *
  * Uso:
  *   import { createObsCollector, login, searchInGrid, ... } from './blazor-e2e-helpers';
@@ -120,7 +120,7 @@ export async function settle(page: Page, extraMs = 0) {
 /**
  * Selecciona la BD en el login si el combo está presente y `DB_ENGINE` está definido.
  * Opt-in y best-effort: si no hay combo, `DB_ENGINE` no está, o algo falla, NO lanza
- * y deja el login directo (comportamiento validado R1-R9 intacto).
+ * y deja el login directo (comportamiento validado).
  * Soporta los dos mecanismos del ERP: DevExpress (SDKDropDownField) y <select> nativo.
  */
 export async function selectDbIfPresent(page: Page, db?: string) {
@@ -151,12 +151,9 @@ export async function selectDbIfPresent(page: Page, db?: string) {
 
 export async function login(page: Page, user?: string, pass?: string, db?: string) {
   const cred = {
-    user: user || process.env.TEST_USER || 'Carlos1',
-    password: pass || process.env.TEST_PASS || '1234',
+    user: user || process.env.TEST_USER || (() => { throw new Error('TEST_USER no definido. Configura TEST_USER en .env'); })(),
+    password: pass || process.env.TEST_PASS || (() => { throw new Error('TEST_PASS no definido. Configura TEST_PASS en .env'); })(),
   };
-  if (!user && !process.env.TEST_USER) {
-    console.warn('[blazor login] TEST_USER no definido — usando credencial demo "Carlos1". Define TEST_USER/TEST_PASS en .env para tu entorno.');
-  }
   await page.goto('/login');
   // Opt-in: solo selecciona BD si DB_ENGINE está definido y el combo existe (si no, login directo).
   await selectDbIfPresent(page, db);

package/siesa-agents/resources/playwright-kit/playwright.config.ts

@@ -59,7 +59,7 @@ export default defineConfig({
     }],
   ],
   use: {
-    baseURL: process.env.BASE_URL || 'https://erp-qa-beta.siesaerp.com',
+    baseURL: process.env.BASE_URL || (() => { console.warn('BASE_URL no definida en .env'); return 'http://localhost:5000'; })(),
     // CI corre en runners Linux sin display → headless obligatorio.
     headless: !!process.env.CI,
     viewport: null,

package/siesa-agents/resources/playwright-kit/reporters/agiletest-reporter.ts

@@ -8,7 +8,7 @@
  *   AGILETEST_CLIENT_ID, AGILETEST_CLIENT_SECRET
  *   AGILETEST_EXECUTION_ID  — ID interno de la ejecución (ej: 115230)
  *   AGILETEST_TC_ID          — ID interno del test case (ej: 1531352)
- *   AGILETEST_PROJECT_ID     — ID del proyecto Jira (default: 10032)
+ *   AGILETEST_PROJECT_ID     — ID del proyecto Jira (requerido, sin default)
  *   AGILETEST_TOTAL_STEPS    — Total de pasos del TC (default: 17)
  *                               Si se ejecutan menos, el TC queda "In Progress"
  */
@@ -23,15 +23,16 @@ import type {
 
 const AGILETEST_BASE = 'https://jira.agiletest.app';
 
-/** Status IDs para proyecto HCM (10032) */
+// Status IDs de AgileTest — cada proyecto Jira tiene IDs diferentes.
+// Configurar en .env si difieren de los defaults.
 const STATUS_IDS = {
-  todo: 15016,
-  pass: 15017,
-  fail: 15018,
-  blocked: 15019,
-  inProgress: 15020,
-  skipped: 15021,
-  retest: 15022,
+  todo:       Number(process.env.AT_STATUS_TODO       || 15016),
+  pass:       Number(process.env.AT_STATUS_PASS       || 15017),
+  fail:       Number(process.env.AT_STATUS_FAIL       || 15018),
+  blocked:    Number(process.env.AT_STATUS_BLOCKED    || 15019),
+  inProgress: Number(process.env.AT_STATUS_INPROGRESS || 15020),
+  skipped:    Number(process.env.AT_STATUS_SKIPPED    || 15021),
+  retest:     Number(process.env.AT_STATUS_RETEST     || 15022),
 } as const;
 
 interface StepResult {
@@ -66,7 +67,7 @@ function readConfig(): AgileTestConfig | null {
     clientSecret,
     executionId,
     tcId,
-    projectId: process.env.AGILETEST_PROJECT_ID || '10032',
+    projectId: process.env.AGILETEST_PROJECT_ID || (() => { console.warn('AGILETEST_PROJECT_ID no definido'); return ''; })(),
     totalSteps: parseInt(process.env.AGILETEST_TOTAL_STEPS || '17', 10),
   };
 }

package/siesa-agents/resources/playwright-kit/specs/architecture-brief-siesa-erp.md

@@ -76,9 +76,7 @@
 
 | Aplicación | Stack | URL base | Auth |
 |-----------|-------|----------|------|
-| Portal de Empleo | Blazor + DevExpress + Radzen | beta-aws.siesadev.com/BLPortalLogin | Email+Password |
-| ERP HCM | Blazor + DevExpress + SDK UI Kit | beta-aws.siesadev.com | MasterCrud + SSO |
-| Encuestas | Blazor + DevExpress + SDK UI Kit | beta-aws.siesadev.com | SSO |
+| ERP Siesa | Blazor + DevExpress + SDK UI Kit | {BASE_URL} | MasterCrud + SSO |
 | Financiero | React 18 + siesa-ui-kit + .NET 8 | qa.finance.siesa.dev/app | SSO |
 
 > **Patrones transferibles:** entity field, SDKSelectField, SDKCharField, TopBarButton,

package/siesa-agents/resources/playwright-kit/tests/seed-example.spec.ts

@@ -1,22 +1,22 @@
 /**
- * seed-gp.spec.ts — Seed file para Playwright Test Agents (GP / HCM)
+ * seed-example.spec.ts — Seed file para Playwright Test Agents (Siesa ERP)
  *
  * Establece el contexto de navegacion: Login ERP + seleccion de BD
  * Usado como referencia por los agentes Planner/Generator/Healer
  *
- * Ambiente por defecto: erp-qa-beta.siesaerp.com (baseURL del playwright.config.ts)
+ * Ambiente: definido por BASE_URL en .env (baseURL del playwright.config.ts)
  * Credenciales y BD se toman de .env (ver .env.example): TEST_USER / TEST_PASS / DB_ENGINE
  */
 import { test, expect } from '@playwright/test';
 
 // ─── Credenciales via env vars (alineadas con .env.example) ────────────────────
 const CRED = {
-  user: process.env.TEST_USER ?? 'Carlos1',
-  pass: process.env.TEST_PASS ?? '1234',
+  user: process.env.TEST_USER ?? '',
+  pass: process.env.TEST_PASS ?? '',
   bd: process.env.DB_ENGINE ?? 'sqlserver',
 };
 
-test.describe('GP HCM — Seed', () => {
+test.describe('Siesa ERP — Seed', () => {
   test('login ERP + verificar dashboard', async ({ page }) => {
     // 1. Navegar al login
     await page.goto('/login');

package/siesa-agents/resources/playwright-kit/tools/locator-recorder.spec.ts

@@ -32,15 +32,15 @@ import * as path from 'path';
 dotenvConfig({ path: path.join(__dirname, '..', '.env') });
 
 const CRED = {
-  user: process.env.TEST_USER || 'Carlos1',
-  password: process.env.TEST_PASS || '1234',
+  user: process.env.TEST_USER || '',
+  password: process.env.TEST_PASS || '',
   dbEngine: process.env.DB_ENGINE || 'sqlserver',
 };
 const OUTPUT_DIR = path.join(__dirname, '..', 'captured-locators');
 const SCREENSHOTS_DIR = path.join(OUTPUT_DIR, 'screenshots'); // v4: visual baseline
 const MODULES_DIR = path.join(OUTPUT_DIR, 'modules');         // v4: modulos reutilizables
 
-// ─── Login reutilizado del flujo encuestas ──────────────────────
+// ─── Login ERP (reutilizable por cualquier modulo) ──────────────────────
 async function login(page: Page) {
   await page.goto('/login');
   await page.waitForLoadState('networkidle').catch(() => {});
@@ -148,7 +148,7 @@ function generatePlaywrightTS(captures: any[]): {
   captures.forEach((c: any) => {
     let base = '';
     if (c.autoId) {
-      // Quitar prefijo SDK: SDKCharField_BLSurvey.Name → BLSurvey_Name
+      // Quitar prefijo SDK: SDKCharField_BLMiModulo.Campo → BLMiModulo_Campo
       base = c.autoId
         .replace(
           /^SDK(CharField|NumericField|Button|DateField|ComboBox|CheckBox|Grid|DataGrid|Dialog|TreeView|RadioGroup|Toolbar|DropDown|ListBox|Tab|Panel|Switch|Menu|Popup|Upload)_/,