Skip to content

integration-testing-results.md

Latest commit

 

History

History
28 lines (20 loc) · 1.93 KB

integration-testing-results.md

File metadata and controls

28 lines (20 loc) · 1.93 KB

Integration and E2E Testing Results

1. Justification & Scope

Integration and E2E tests validate the end-to-end functionality of the UMS Mono-repo. The scope comprehensively covers all three architectural tiers:

  • Web (Frontend): Playwright E2E tests validating the React SPA UI rendering, state management, and user flows.
  • API (Backend): Integration tests invoking live GraphQL and REST endpoints, validating request parsing, AOP authorization interceptors, and response mapping.
  • DB (Database): Validation of actual PostgreSQL queries, row-level security policies, and data persistence triggered by the API layer in a real database container/instance.
  • Key Scenarios: Authentication Flows, Tenant Isolation (RLS and Application Level), Role Authorization, Navigation, and Dynamic UI Rendering.

2. Executed Cases & Results

Based on the latest QA cycle:

  • Total E2E Tests Executed: 35
  • Passed: 1
  • Failed: 34
  • Status: FAIL (due to recent UI label shifts, not business logic errors).

Key Covered Scenarios & Findings

  • Authentication Flow: Validates login, session expiry, and locked accounts. Failing strictly because UI labels like 'Usuario' were updated to 'Correo electrónico' for OWASP compliance.
  • Dynamic Authorization UI: Validates that buttons (e.g., 'Agregar') are disabled or enabled based on dynamic permissions (AOP interceptors on the backend reflect properly via the UI).
  • Navigation & Profile Panel: Validates session drawer data, tenant active state, and module access.

3. Conclusions & Next Steps

The business logic integration (API responses, HTTP status codes, security interceptors) has been manually verified and is stable. The automated E2E tests are failing strictly due to DOM selector mismatches resulting from recent security hardening updates in the UI.

Action Item: Update Playwright getByText and getByLabel selectors to match the new OWASP-compliant UI labels.