Quality Analyst, Not Quality Assurance.
Translate production traffic and user journeys into concurrency, arrival rates, pacing, and data variation to build a realistic, repeatable load test.
Classify intermittent failures by timing, data, order, environment and product behavior before deciding to repair, quarantine or monitor.
Set regression scope from change evidence, dependency paths and risk; state which behaviors are covered, deferred or still exposed.
Choose regression tests by affected contracts, user impact and defect history, preserving fast feedback while recording uncovered risk.
Trace code changes through behavior, dependencies, data and consumers to identify tests that need fresh evidence and risks that remain.
Review test code for assertion quality, isolation, determinism, and boundary risks so a green result reflects reliable behavior.
Trace changed files through dependencies and call paths to select risk-based regression checks that cover affected behavior, not just directories.
Keep Java API requests, contract assertions, and failure diagnostics readable with REST Assured so reviews can see intent and evidence.
Test Node API behavior at the HTTP boundary with Supertest, including authentication, payload validation, and error responses without framework coupling.
Build isolated pytest API checks with clear fixtures, client calls, and failure assertions while keeping external dependencies outside the test boundary.
Derive contract examples from consumer expectations to catch incompatible API changes before independently deployed services disagree in production.
Make Bruno collections portable and reviewable by versioning requests, environments, and assertions; keep local runs and CI on the same contract.
