SUDARSHANCHAUDHARI

api-qa

Plans and executes API validation across contracts, authentication, authorisation, data integrity, errors, pagination, rate limits, idempotency, concurrency, and compatibility.

AI & Automation Solid

automation-review

Audits an automated test suite for correctness, reliability, isolation, maintainability, coverage value, security, runtime cost, and false-confidence patterns.

Data & Documents Solid

bug-report

Converts an observed problem into a precise, reproducible, environment-bound defect report without overstating cause, severity, or scope.

bug-triage

Reviews an incoming issue and determines what it most likely represents, how severe it is, who should own it, what evidence is missing, and what action should happen next.

customer-issue-repro

Transforms a support case into a privacy-safe, controlled reproduction plan that compares customer conditions with known-good conditions and returns a clear confidence-based outcome.

exploratory-qa

Runs a time-boxed exploratory session with a clear charter, controlled data, evidence, notes, coverage map, findings, and follow-up recommendations.

feature-qa

Turns a ticket and its implementation into a version-bound, evidence-backed QA run with explicit approvals, deterministic release rules, regression protection, publication, and cleanup.

flaky-test-triage

Diagnoses inconsistent test results by separating product nondeterminism, automation defects, shared data, timing, infrastructure, environment, order, and concurrency effects.

network-qa

Investigates connectivity failures across interfaces, DNS, proxy, TLS, firewall, redirects, private-network rules, endpoints, and application behaviour while protecting network and customer secrets.

offline-qa

Validates startup, cached operation, interruption, reboot, clock changes, queued work, reconnection, synchronization, and long-offline limitations with explicit observation duration.

permission-qa

Validates authentication and authorisation across roles, tenants, ownership states, endpoints, operations, cached sessions, and direct-object access.

platform-matrix

Builds and maintains a defensible compatibility matrix across browsers, operating systems, devices, firmware, resolutions, roles, regions, and feature states.

playback-qa

Validates media startup, decoding, layout, looping, transitions, audio, synchronization, interruption, recovery, long-running stability, and platform-specific rendering.

qa-daily-summary

Produces a concise daily or stand-up update from verified work records without inventing progress, hiding blockers, or exposing restricted detail.

qa-handoff

Creates a precise handoff so another tester or team can continue from the correct build, state, evidence, and next action without repeating work or losing uncertainty.

qa-retrospective

Reviews a completed release, incident, project, or testing cycle to identify escaped-risk patterns, process failures, effective controls, and owned preventive actions.

regression-scope

Determines the smallest defensible regression set for a change by combining code impact, architecture, risk, historical failures, platform exposure, and operational behaviour.

release-qa

Combines ticket-level results, open defects, platform coverage, rollout safeguards, monitoring, rollback readiness, and accepted risk into one auditable release recommendation.

smoke-test

Runs a short, version-bound health check across the most critical user and system paths to decide whether deeper testing or rollout should continue.

staged-rollout-check

Evaluates each rollout stage using version adoption, product health, device state, support signals, cohort comparison, and predefined rollback thresholds.

test-case-review

Audits existing manual test cases for correctness, clarity, traceability, duplication, maintainability, execution value, automation suitability, and obsolete assumptions.

test-plan

Creates a reviewable test plan from approved requirements, implementation context, and known risk, with explicit scope, required scenarios, evidence, data, and exit criteria.

ticket-review

Reviews a Jira or Linear ticket before implementation or QA begins, exposing ambiguity, contradiction, hidden dependencies, missing acceptance criteria, and untestable expectations.

verify-fix

Determines whether a reported defect is fully fixed in the intended build and whether related behaviour remains safe across the agreed regression scope.