Projects & testing outcomes

The challenge

Multi-role permissions, real-time availability, and money-adjacent booking flows meant a single missed edge case could double-book a hangar or expose another operator's data.

Testing strategy

• Mapped every user role against every action to build an explicit permission matrix, then tested each cell rather than sampling.
• Validated all API endpoints in Postman, including negative cases: expired sessions, tampered IDs, and out-of-range dates.
• Checked transactional integrity directly in PostgreSQL after each booking flow to confirm no partial writes survived a failure.
• Coordinated fixes and re-tests through Jira, keeping a clean audit trail from report to verification.

The challenge

Location tracking and payment both fail in ways an emulator never shows — dropped GPS signal, backgrounded apps, interrupted payment callbacks — and any of them loses a real customer's money or ride.

Testing strategy

• Tested on physical Android and iOS devices, not just simulators, to catch platform-specific behaviour.
• Simulated GPS movement and signal loss to verify tracking recovered instead of silently stalling.
• Exercised payment flows against gateway test modes, including declines, timeouts, and duplicate submissions.
• Verified push notification delivery across foreground, background, and terminated app states.

The challenge

ERP modules share data, so a defect in one screen surfaces as corrupted totals three modules away — and the UI often looks correct while the underlying records are not.

Testing strategy

• Traced each business workflow end to end across modules instead of testing screens in isolation.
• Wrote SQL queries against MS SQL Server to verify what was actually persisted after each operation.
• Built a regression suite around the highest-risk financial calculations and re-ran it every release.
• Ran UAT sessions with client stakeholders, translating their business language into reproducible test cases.

The challenge

In eCommerce every checkout defect is lost revenue, and the failure modes cluster in exactly the places that are tedious to test: cart state, stock counts, and price totals.

Testing strategy

• Tested the full purchase path — browse, filter, cart, checkout, confirmation — including abandoned and resumed carts.
• Verified totals, discounts, and stock decrements against the database rather than trusting the displayed value.
• Ran cross-browser checks on the catalogue and checkout to catch layout and validation differences.
• Confirmed order records and status transitions in the admin panel matched what the customer saw.