QA
Tester

Keeps the regression pack in TestRail, Xray or Zephyr current: retires cases for removed features, adds cases for shipped stories, and tags by risk so a hotfix run can cover payment and login paths without executing the whole library.

Reads the story and acceptance criteria before development finishes, writes positive, negative and boundary cases with explicit preconditions and expected results, and raises the ambiguities — what happens on a duplicate submission — as questions on the ticket rather than assumptions.

Works the run in the test management tool against the release candidate build, marks each case passed, failed or blocked with evidence attached, and hands the release manager the outstanding defect list before the go/no-go call.

Logs defects in Jira with build number, environment, exact steps, actual versus expected result, console and network output, and a screen recording — so the developer is not guessing whether it is data, browser or genuinely code.

Retests each fixed defect on the build it claims to be fixed in, runs the surrounding cases to catch what the fix broke on the way past, and reopens with fresh evidence rather than accepting a status change.

Runs the critical journeys across the browser and device matrix agreed for your customer base, using BrowserStack or physical handsets, checking layout, form input behaviour under mobile keyboards, and the things that only ever break on Safari.

Exercises endpoints in Postman against the documented contract — status codes, required fields, validation messages, authentication failures, malformed payloads — and confirms the record actually landed in the downstream system rather than trusting a 200 response.

Runs timed charter-based sessions across new or historically fragile areas, hunting what nobody scripted: back button mid-checkout, session timeout on a long form, pasted data carrying unusual characters, and writes findings up against the charter.

Prepares the UAT environment and data, writes the scripts your business users follow, sits in the sessions to capture what they actually hit, and triages their reported issues into defects, training gaps or genuine change requests.

Sets up the accounts, orders, subscription states and edge-case records each cycle needs, refreshes them after environment resets, and keeps a documented seed set for the scenarios that are painful to construct by hand every time.

Runs keyboard-only navigation, screen reader spot checks and automated axe scans across key pages, and logs missing form labels, focus traps and contrast failures against the specific WCAG success criterion rather than a general complaint.

Publishes a short daily status through a release cycle — cases executed, cases blocked and what is blocking them, defects by severity still open, areas not yet covered — so the project lead can see whether the date is real.