CLINTON NKWEKE · QA ANALYST
● OPEN TO WORK
BUG-0001 · reported by every user, eventually SEVERITY: CRITICAL

Your product shipped without a QA analyst.

Steps to reproduce
  1. Build the product
  2. Skip structured testing
  3. Release to production
Actual result

Payment failures, angry reviews, 2 a.m. hotfixes and a support inbox on fire.

Expected result

Defects caught before release — by someone who tests like a user and documents like an engineer.

Resolution

Hire Clinton Nkweke. Manual & API testing across banking, ecommerce and e-hailing. Three full case studies below.

View test suites ↓ Log a ticket (contact)
3
Test suites
379
Test cases written
94
Defects logged
17
Critical / high severity
01 /

Test coverage

The types of testing I run, the tools I run them with, and the artifacts I leave behind so anyone can retrace my steps.

Testing types

FunctionalRegression Smoke & sanityExploratory API testingUAT support Cross-browserMobile (Android) UsabilityNegative testing

Tools & tech

JiraTestRail PostmanSQL Chrome DevToolsCharles Proxy Selenium (basics)Git ConfluenceTrello

Artifacts I produce

Test plansTest cases Bug reportsRTM (traceability) Test summary reportsExploratory charters API collectionsRelease sign-off notes
02 /

Test suites — three case studies

Structured, hands-on QA case studies on realistic applications. Each suite includes a full test plan, executed test cases, and a defect log with severity classification.

SUITE-01 · digital banking WEB · API

NovaBank — retail banking web app

End-to-end functional and API testing of a digital banking platform: onboarding with KYC, login and 2FA, intra-bank and interbank transfers, transaction limits, and statement export. Security-adjacent negative testing on sessions and input validation.

148
Test cases
41
Defects logged
8
Critical / high
96%
Requirement coverage

Scope tested

  • Account opening & KYC document upload flow
  • Login, OTP / 2FA, and session management
  • Funds transfer — same bank, interbank, scheduled
  • Daily transaction limits & balance validation
  • Transfer APIs via Postman — auth, status codes, error payloads
  • Statement generation & PDF/CSV export

Highest-impact defects found

CRITICAL
NB-014Transfer API accepted a negative amount, crediting the sender when called directly with a crafted payload.
HIGH
NB-027Active sessions not invalidated after password change — old session could still initiate transfers.
MEDIUM
NB-033Rounding error on scheduled transfers with 3-decimal input caused a ₦0.01 ledger mismatch per transaction.
ARTIFACTS: Test plan RTM Postman collection Defect log (Jira) Summary report
SUITE-02 · ecommerce WEB · CROSS-BROWSER

Cartly — online storefront & checkout

Functional, regression and cross-browser testing of a full purchase journey: search and filters, cart behaviour, coupon logic, checkout with multiple payment methods, and order lifecycle from confirmation to cancellation and refund.

126
Test cases
32
Defects logged
5
Critical / high
4
Browsers covered

Scope tested

  • Product search, filtering & sorting accuracy
  • Cart persistence across sessions and devices
  • Coupon & promo logic, including stacking rules
  • Checkout — card, wallet and pay-on-delivery paths
  • Payment failure & timeout handling mid-checkout
  • Order tracking, cancellation & refund states

Highest-impact defects found

CRITICAL
CT-009Two rapid checkouts of the last unit in stock both succeeded — inventory oversell with no back-order handling.
HIGH
CT-018Expired coupon still applied at payment step if added to cart before expiry — discount honoured on settlement.
MEDIUM
CT-024On Safari, payment timeout returned user to an empty cart while the order was actually created — duplicate orders.
ARTIFACTS: Test plan Cross-browser matrix Regression pack Defect log (Jira) Summary report
SUITE-03 · e-hailing MOBILE · ANDROID · API

SwiftRide — ride-hailing mobile app

Mobile-first testing of rider and driver flows on Android: ride requests and matching, fare estimation vs final fare, live GPS tracking, surge pricing display, cancellations and refunds, plus network-condition testing on poor connectivity.

105
Test cases
21
Defects logged
4
Critical / high
6
Devices tested

Scope tested

  • Rider signup, phone verification & profile setup
  • Pickup pin accuracy & saved-location handling
  • Fare estimate vs final charge reconciliation
  • Ride lifecycle — request, match, trip, complete, rate
  • Cancellation fees & refund flows on both sides
  • Offline / flaky-network behaviour (2G, airplane toggle)

Highest-impact defects found

CRITICAL
SR-006Rider charged full fare when driver cancelled mid-trip after app lost network — no automatic refund raised.
HIGH
SR-011Surge multiplier shown on estimate but silently dropped at payment, undercharging riders during peak hours.
MEDIUM
SR-017Pickup pin drifted ~200m in dense areas when GPS accuracy was low, with no prompt to confirm location.
ARTIFACTS: Test plan Device matrix Exploratory charters Defect log (Jira) Summary report
03 /

How I test

STEP 1

Analyse

Read requirements and user stories, question ambiguity early, and map risk — what breaks the business if it breaks?

STEP 2

Design

Write traceable test cases covering happy paths, edge cases and negative scenarios, prioritised by risk.

STEP 3

Execute & log

Run planned and exploratory sessions, then log defects with clear repro steps, evidence and severity a developer can act on.

STEP 4

Report & retest

Verify fixes, run regression, and hand over a summary report that lets the team make a confident release call.

04 / LOG A TICKET

Assign your next release to me.

I'm available for QA Analyst roles — remote or hybrid. Send a message and I'll respond with the same speed I triage a critical defect.

Email me LinkedIn GitHub Call +234 913 658 1704