API testing with Postman and JMeter
The screen only shows part of the story. I check the API and the data behind it, to confirm that what users see matches what the system actually does.
What I check
- REST API responses and integrations, using Postman.
- Data integrity, comparing what is shown on screen with what the API returns and what is stored in the database (I use SQL for database checks).
- Application performance under load, using Apache JMeter.
- Access rules at the API level, not only in the interface.
Where it matters most: payments
On Getways, a payment and gaming transaction platform, I validated integrations with WERT, Stripe, Coinbase, Fiserv, CLKK and PayNearMe across Player, Agent, Master Agent and Super Admin journeys. That work produced 1,642+ test cases and 420+ defects.
How I test a payment flow
- Read the rules first: limits, fees, currencies and who is allowed to pay.
- Test the happy path with each payment method.
- Break it: declined cards, timeouts, double clicks, refreshing mid-payment, closing the tab.
- Check the numbers: amount, fee and balance must match on screen, in the API and in the database.
- Check every role sees only what it should.
- Automate the stable core, then re-run it after every release.
Example: a duplicate request found through the network tab
In an illustrative defect report, double-clicking Submit on a withdrawal created two requests and took 100 from a balance of 100 instead of 50. The evidence was a screen recording plus the duplicate API calls in the network tab. The suggested fix was to lock the button on the first click and make the endpoint reject duplicates. The full report is on my manual testing page.
Example: access control at the API
A sample scenario from my role-based access test cases: a player calls an admin API with a valid player token, and the server should return 403 with no data. A hidden menu item is not enough. The server has to refuse the request.
Load testing
I run load tests in Apache JMeter to see how an application performs beyond what one tester clicking through the UI can show.
For the UI side of the same flows, see Playwright automation.