Context

A backend application introduced principal preorder transactions with interconnected pricing, tax, discount, customer, product, payment, printout, credit-limit, and cash-limit behavior.

QA Role

I planned coverage for the preorder lifecycle and its financial calculations, prepared representative customer and product data, and supported UAT. UI results were compared with API responses and MySQL records to confirm that tax, discount, payment, and limit values agreed.

Testing Scope

• Preorder transaction flow
• PPN calculation
• Product discounts and price display
• Customer and product management
• Payment creation
• Transaction printouts
• Available credit and cash limits

Test Approach

Calculation risk drove the strategy. Boundary values around PPN, discounts, available credit, and cash limits were verified independently, then rechecked through payment creation and transaction printouts.

Tools

Postman, MySQL, Jira, Google Drive, and Visual Studio Code.

Methods & Formats

Gherkin / BDD.

Project Evidence Set

Test Case

Boundary and scenario coverage for PPN, discounts, price display, payment creation, printouts, and credit-limit usage.

API Testing

Postman assertions for transaction totals, payment responses, limit values, and negative calculation paths.

SQL Validation

Reconciliation of displayed totals, stored transaction values, payment records, and available credit adjustments.

Gherkin / BDD

Readable behavior scenarios for preorder pricing, payment, credit-limit, and printout rules.

Bug Report

Defect evidence for calculation mismatch, payment behavior, printout inconsistency, and limit validation.

Traceability Matrix

Mapping from pricing and limit rules to test scenarios, API/database checks, execution status, and residual risk.

UI Automation

Cucumber and Selenium POM structure for repeatable UI checks on stable preorder flows.

Business Impact

The team gained clearer evidence that displayed totals, stored values, credit usage, payment records, and printed output represented the same transaction.

Confidentiality

This case study reflects real QA responsibilities. Product rules, identifiers, and selected details have been generalized to protect confidential information.

All Projects