Test Strategy & Planning
Risk-based test plans, scope and coverage analysis, traceability from acceptance criteria to test cases.
- Risk analysis
- Test plans
- Traceability
- Exploratory
Available for QA roles & projects
I find the bugs
before your users do.
I'm Mark Ariel Quines, a Quality Assurance engineer who turns requirements into risk-based test plans, automated regression suites and release decisions teams can trust.
$ npm test -- --reporter=verbose
RUN release-candidate
✓ auth › role permissions enforced
✓ sales › split payment totals
✓ sales › refund restocks inventory
✓ stock › reorder alert threshold
✓ clients › search by name & phone
✓ receipts › exchange receipt prints
Test Files 42 passed
Tests 450 passed
Status READY TO SHIP450automated test cases written for a single client app
42test files across UI, server actions & data rules
4CI quality gates on every pull request
0merges to main without a green pipeline
01 — About
Quality is a team habit. I help build it.
I treat QA as more than finding defects at the end of a sprint. I get involved at the requirements stage, ask the questions that expose ambiguity early, and map every feature to the risks that matter most to the business: money, data and access.
From there I design the right mix of manual exploration and automated checks, wire them into CI so regressions are caught on every pull request, and report clearly so stakeholders can make confident release decisions.
- Requirements reviewed for testability before code is written
- Acceptance criteria turned into traceable test cases
- Edge cases hunted: refunds, partial payments, time zones, permissions
- Bug reports with clear steps, evidence and impact
02 — Skills
A toolkit for every layer of quality
Test Automation
Maintainable unit, component and integration suites that run fast and fail for the right reasons.
- Vitest
- Testing Library
- Playwright
- TypeScript
API & Data Testing
Contract and boundary checks for endpoints and server actions, validation rules and database integrity.
- REST
- Zod schemas
- SQL
- Seed data
CI/CD Quality Gates
Lint, type-check, test and build gates on every pull request so nothing broken reaches main.
- GitHub Actions
- ESLint
- tsc
- Code review
Cross-device & UX
Responsive and tablet-first checks, accessibility basics, usability feedback grounded in real workflows.
- Responsive
- WCAG basics
- Usability
Process & Reporting
Clear defect reports, release readiness summaries and Agile collaboration with devs and product.
- Jira
- Agile/Scrum
- Bug triage
- Git
03 — Experience
Where I've put quality to work
-
QA & Test Engineer — Clinic Record, Sales & Stock Management App
Owned quality for a tablet-first web app used by a clinic's front desk, nurses and admins to manage client records, visits, point-of-sale and inventory.
- Reviewed the client's requirements into a written spec, plan and task list, resolving open questions before build.
- Built a suite of ~450 automated tests across 42 files covering sales, refunds, exchanges, stock and role permissions.
- Set up CI so every pull request must pass lint, type-check, tests and a production build.
- Hardened flaky behaviour, e.g. making return-window tests independent of the time of day.
-
Continuous learning in Quality Engineering
Deepening skills in end-to-end automation, API testing and test design techniques: boundary values, equivalence partitioning, state transitions and decision tables.
04 — Projects
Featured case study
Healthcare · Point of sale · Inventory
Clinic Record, Sales & Stock Management
A small clinic needed one tool for client records, visit history, split-payment sales, thermal receipts and stock counts, with five staff roles and different permissions. The risk: money and medical data. A wrong refund, a stock count that drifts, or a nurse seeing an admin-only action would erode trust fast.
What I tested
- Role-based permission matrix
- Split payments & discounts
- Voids, refunds & exchanges
- Stock movement & reorder alerts
- Forms, validation & receipts
How
- Spec → plan → tasks traceability
- Vitest + Testing Library
- Isolated test DB & fixtures
- Deterministic, time-safe tests
- GitHub Actions gates
Sales & refundscovered
Permissionscovered
Stock & inventorycovered
Client recordscovered
- Test cases
- ~450
- Test files
- 42
- PRs gated
- 100%
Bars show relative focus areas, not a coverage tool's output.
Bug report template
Title, environment, steps, expected vs actual, evidence, severity and impact, so any developer can reproduce an issue in minutes.
Release readiness checklist
Green CI, regression pass on critical paths, open-defect review and a go/no-go summary written for non-technical stakeholders.
05 — Process
How I approach a release
- 01
Understand
Read requirements, map users and data flows, ask the awkward questions early.
- 02
Assess risk
Rank features by business impact and likelihood of failure to focus effort.
- 03
Design tests
Boundaries, partitions, states and negative paths, traced to acceptance criteria.
- 04
Automate
Fast, deterministic suites running in CI on every pull request.
- 05
Explore
Session-based exploratory testing where scripts can't think like a user.
- 06
Report
Clear defects and a release summary the whole team can act on.
06 — Contact
Need confidence in your next release?
I'm open to QA engineer roles and freelance testing projects. Let's talk about what you're shipping.