Risk & Experience Based Testing
A release is tomorrow, but QA has very limited time. What should be tested first?
QA Engineer · Abu Dhabi, UAE
I test the systems people trust with their money — and the AI systems being trusted with everything else. Currently leading QA for a merchant acquiring platform: CIT/MIT-compliant payment flows, dynamic currency conversion, and card/settlement data integrity. Previously validated AI models for static analysis, requirements engineering, and inbox automation.
01 · Featured Videos
Clips from internal lectures and testing explainers I post on LinkedIn — real content, not just a static repo link.
A release is tomorrow, but QA has very limited time. What should be tested first?
Four words QA engineers use constantly and often blur together — broken down simply.
Load, stress, soak, spike, scalability, and endurance testing — what each one actually catches.
A live walkthrough introducing static testing concepts from the ISTQB Foundation syllabus.
Why "minor" bugs get treated as critical the moment they touch money — a lesson from payment QA.
02 · About
I'm an ISTQB-certified QA engineer (Foundation, Test Automation Engineer, Performance Testing, Automotive) with hands-on experience across manual and automated testing for web, mobile, and API applications. I've worked in Agile teams alongside European clients, built Python tooling to generate test cases and reports, and moved from safety-critical automotive systems into fintech and AI-system validation — domains where a missed edge case has real consequences.
03 · Experience
Merchant Acquiring & Payment Core — Botim Payment Platform
Leading QA for a merchant acquiring & payment core platform processing millions of transactions — CIT/MIT-compliant payment flows (the Visa/Mastercard stored-credential framework), recurring/tokenized payments, dynamic currency conversion (DCC), card data integrity, and the merchant-facing admin portal.
Validated three distinct AI systems — a static-analysis model, an NLP requirements checker, and an email-classification pipeline — each requiring a different definition of "correct."
04 · AI Testing Deep Dive
Traditional QA checks output against a spec. Testing AI systems means testing a distribution of plausible outputs — these three projects each demanded a different strategy.
An AI tool flagging MISRA C/C++ rule violations. I built graded test files spanning multiple sizes and violation densities to measure the model's precision and recall, then verified coverage across the key rule groups (8.x, 10.x, 11.x, 15.x, 20.x, 21.x) before reporting reasoning gaps back to the team.
An NLP tool assessing SYS.2/SWE.1 requirements against ASPICE Base Practices BP1–BP4. I validated outputs for feasibility, verifiability, atomicity, and consistency, then stress-tested it with malicious input and oversized files to check where the model's judgment broke down.
A Gmail-connected classifier sorting inbound mail into Inquiry, Order, Complaint, and Other. I verified classification accuracy alongside an automated Excel-extraction engine, testing structured-data parsing, missing-field detection, corrupted files, and multilingual inputs.
05 · Open-Source QA Projects
Nine self-contained repos demonstrating manual and automated testing across the layers a payments and AI/ML QA engineer touches daily — UI, mobile, API, performance, security, ML model evaluation, LLM testing, and structured manual test design.
TypeScript + Playwright, Page Object Model. 38 tests across login, inventory, cart, and checkout — including cross-browser CI and independently-recomputed order-total math checks.
View on GitHub →Java + Appium + TestNG, Page Object Model for native Android. 30 tests across login, catalog, cart, and drawer navigation, with an emulator-based CI workflow.
View on GitHub →Dual-track API testing: REST Assured + TestNG (Java) and a Postman/Newman collection, ~30 tests including JSON schema validation and data-driven negative cases.
View on GitHub →A full manual-QA artifact set: ISTQB test-design techniques, 160+ test cases, bug reports, and a requirements traceability matrix — spanning checkout, and API/DB/UI/performance/security suites for a fictional payment & wallet platform.
View on GitHub →REST Assured + TestNG and Postman/Newman against Stripe's real test-mode API — 30 tests covering payment intents, refunds, decline scenarios, idempotency, and the 3D Secure automation boundary.
View on GitHub →k6 + JMeter load testing against a self-contained mock payment service — baseline, spike, soak, and a concurrent-refund race-condition check. Every number in the README is a real local-run result.
View on GitHub →OWASP API Security Top 10 applied to a payment API. An intentionally vulnerable mock service plus a dual Python/pytest + Postman suite that independently confirms 5 real, exploitable findings.
View on GitHub →Precision/recall/F1 benchmarking of a real Hugging Face sentiment model across 74 hand-curated cases, plus adversarial/robustness and directional fairness-probe testing.
View on GitHub →Consistency, structured-output validation, prompt-injection resistance, hallucination spot-checks, and refusal-boundary testing against a deterministic mock LLM with real, seeded findings.
View on GitHub →06 · Skills
07 · Certifications
08 · Contact
Open to QA / SDET roles in fintech, mobile, and AI-product testing.