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 of the Diploma Tracking System (DTS), a real full-stack academic platform I work on.
UI (Frontend)
In ProgressPlaywright E2E suite with page objects, auth fixtures, and business-flow tests. Covers login, dashboard, RBAC navigation, student progress. Expanding coverage.
API (Backend)
StrongIntegration + smoke + exploratory tests covering auth, RBAC, student flows, admin flows, enrollment rules, and data isolation. 15 route files, consistent JWT + Zod pattern.
Database
PartialSupabase RLS policies tested via API layer. Direct DB integration tests via Supabase client. Migration-based schema with audit logging.
CI / CD
Solid6 GitHub Actions workflows: typecheck + unit + API on push, daily smoke, weekly regression with Playwright video, production validation, UX guard. Public Allure report dashboards deployed to GitHub Pages after every run.
Live Allure Dashboards
CI-generated test report dashboards deployed to GitHub Pages — live after every run.
Live Project: bunkai-tms + DTS
Real bug findings from production apps tested with Playwright, Cucumber, and Allure Reports — integrated with Jira for traceability. 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