Quality Engineering
Philosophy, strategy, and evidence from real projects.
My QA Approach
Quality Engineering is a design discipline, not a testing phase. I believe in shift-left thinking — finding issues before they become bugs, building testability into architecture, and using automation to amplify human judgment, not replace it.
Testability Scorecard
A layered assessment across three real projects: Diploma Tracking System (full-stack academic platform), the Agentic QA Boilerplate (open-source AI-driven test framework), and UNC Campus Virtual (Moodle automation & course audit).
UI (Frontend)
Playwright E2E suite across DTS (page objects, auth fixtures, business-flow tests) and unc-agentic-dev (course audit across student/teacher/admin roles). Covers login, dashboard, RBAC navigation, student progress, a11y compliance, and Moodle course structure validation. Allure dashboards with run history.
API (Backend)
End-to-end integration, smoke, and exploratory test suites covering auth (JWT), RBAC, enrollment rules, data isolation, and API contract validation across the Agentic QA Boilerplate and DTS. Plus Moodle REST API audit in unc-agentic-dev validating course structure, grade conditions, and section restrictions. Consistent JWT + Zod pattern across 15+ route files.
Database
Supabase RLS policies tested via API layer — validating data isolation, enrollment rules, and multi-tenant boundaries across the Agentic QA Boilerplate and DTS. Direct DB integration tests via Supabase client. Migration-based schema with audit logging.
CI / CD
17 GitHub Actions workflows across 4 repositories: typecheck + unit + API on push, daily smoke with Allure, weekly regression with Playwright video, production validation, UX guard, course audit CI (workflow_dispatch for on-demand audits). Public Allure dashboards deployed to GitHub Pages after every run.
Traceability (TMS)
@atc decorators map automated tests to Jira/Xray test cases, synced through a 13-command Xray CLI (import, exec, link, trace, backup/restore). Structured evidence conventions tie every defect to screenshots and test-case IDs for full end-to-end traceability.
Live Quality Evidence
CI-generated Allure dashboards deployed to GitHub Pages — live after every run — plus the open-source framework that produces them.
Live Projects: Agentic QA Boilerplate + DTS + unc-agentic-dev
Real bug findings from production apps tested with Playwright, Cucumber, and Allure Reports — integrated with Jira for traceability. Course audit screenshots from UNC Campus Virtual Moodle automation. Allure dashboards live at /qa/dashboard.
Allure smoke test report — automated test suite results overview
Allure test details — test cases with steps, parameters, and history
Jira board — QA workflow integration with traceability
App shell with sidebar — layout integrity check
Multi-tab navigation — state consistency across tabs
TC-10: Not found state — missing 404 handling on invalid routes
Course 269 — Section 0: Bienvenida audit — 10 modules, no restrictions
Course 269 — Section 4: Cierre audit — grade conditions detected
Admin exploration — course edit mode with full layout