Four review-ready reference frameworks for browser, API, accessibility, visual, and performance engineering. Each repository is designed to be reviewed, run, challenged, and adapted.
Explore the evidence dashboard · Review the repositories · LinkedIn
This is not a collection of sample tests. It is a portfolio of automation systems with explicit architecture, controlled execution targets, measurable CI behavior, failure evidence, reliability policies, security controls, and release discipline.
| Engineering surface | Repository | What to inspect first |
|---|---|---|
| Performance and reliability | k6 Performance | SLO gates, six workload models, regression baselines, Grafana, OpenTelemetry |
| Modern browser, API, visual, accessibility | Playwright TypeScript | Typed fixtures, controlled target, sharded CI, visual baselines, Axe, Allure |
| API contracts and security boundaries | ARIA API | Service layers, Pact, OpenAPI coverage, deterministic provider, redacted diagnostics |
| Enterprise browser execution | Selenium TestNG Java | Grid matrix, parallel drivers, typed configuration, failure diagnostics, governance |
| Order | Repository | Reviewer question | Time |
|---|---|---|---|
| 1 | Portfolio dashboard | Are the CI, runtime, releases, and evidence current? | 3 min |
| 2 | k6 Performance | How are load safety, SLOs, baselines, and observability engineered? | 12 min |
| 3 | Playwright TypeScript | How is a broad test strategy kept deterministic and maintainable? | 12 min |
| 4 | ARIA API | How are contracts, schemas, security checks, and diagnostics layered? | 10 min |
| 5 | Selenium TestNG Java | How does the design scale across browsers, threads, and Grid capacity? | 10 min |
| Repository | CI | Report | Release | Review guide |
|---|---|---|---|---|
| Playwright TypeScript |  |
Allure | v1.0.0 | Review path |
| k6 Performance |  |
Performance reports | v0.4.0 | Evidence guide |
| ARIA API |  |
Allure | v1.0.0 | Review path |
| Selenium TestNG Java |  |
Allure | v1.0.0 | Review path |
- Determinism: controlled targets, seeded data, pinned runtimes, and reproducible commands.
- Reliability: explicit retry budgets, quarantine rules, runtime metrics, and flake triage.
- Diagnostics: screenshots, logs, traces, request evidence, and actionable failure examples.
- Architecture: documented trade-offs, ADRs, ownership boundaries, and extension points.
- Governance: CI quality gates, dependency scanning, SBOMs, release notes, and reviewer paths.
- Honesty: limitations, target realism, and professional claims are labeled precisely.
flowchart LR
O["QA Test Automation Frameworks"] --> P["Playwright\nbrowser + API"]
O --> K["k6\nperformance"]
O --> A["ARIA\nAPI contracts"]
O --> S["Selenium\nenterprise UI"]
P --> E["Shared evidence standard"]
K --> E
A --> E
S --> E
E --> C["CI · reports · metrics · failures · ADRs · releases"]
The automation platform scaling case study connects the repository evidence to anonymized professional experience with suite growth beyond 10,000 automated checks, CI feedback constraints, reliability governance, migration, and cross-team operating standards.
The fastest way to evaluate this work is to open the evidence dashboard, choose a framework, inspect its latest CI and failure evidence, then run its documented local quality gate.
