Manual, functional and regression testing

Manual testing is where I learn how a product really behaves: who uses it, what the rules are and where it can go wrong. Here is how I work and what it looks like on the page.

The types of testing I run

My process

  1. Read the requirements like a skeptic. Challenge assumptions and list the risks.
  2. Design test cases from the business requirements and acceptance criteria.
  3. Explore real user scenarios across roles and workflows.
  4. Log defects in JIRA with clear steps, expected and actual results, and evidence.
  5. Retest fixes, run regression, and close the defect.

Where I’ve used it

AgroPack ERP: 3,500+ test cases, 350+ defects

A manufacturing and quality control system for agrochemicals. I tested workflows across 7 enterprise roles: sample management, batch creation, laboratory testing, chemical inventory, production approval, COA workflows and packaging plant controls.

Vegas Empire: 2,160+ test cases, 260+ defects

On the admin portal I tested user management, game CRUD, game coins, RTP, bonus features, recharge and redeem, support tickets and chat under a multi-level role hierarchy. On the player site I played through 100+ slot games, checking gameplay and functionality as a real player would.

Sample test cases: role-based access

An illustrative set that shows how I write scenarios and set priority. It uses no client data.

IDScenarioExpected resultPriority
RBAC-02Agent opens the Super Admin URL directlyAccess is denied and the user is redirectedHigh
RBAC-03Agent views the user listOnly their own downline is shownHigh
RBAC-04Agent creates a user under another agentAction is blocked with a clear messageHigh
RBAC-06Role is changed while the user is logged inNew permissions apply after refresh or next loginMedium
RBAC-07Disabled user tries to log inLogin fails with a clear messageMedium

Sample defect report

Withdrawal is created twice when Submit is double-clicked

Severity: Critical. Priority: High. Environment: QA, Chrome on Windows. Role: Player.

Steps: log in as a player with a balance of 100, open Withdraw, enter 50, double-click Submit quickly.

Expected: one withdrawal of 50 is created and the button locks after the first click.

Actual: two withdrawal requests appear in history and the balance drops by 100.

Evidence: a screen recording and the duplicate API calls from the network tab.

Suggested fix: disable the button on first click and make the endpoint reject duplicate requests.

Once a flow is stable I automate the core of it. See Playwright automation, and for checks beyond the UI, API testing.

More from my portfolio

Have something that needs breaking?

I’m open to remote QA roles.

Email meLinkedInResume (PDF)