What skills does Asadullah Kissana have?

Testing disciplines

Manual and exploratory testing. The core of the work, and the part that finds defects a script never would, because it follows suspicion rather than a checklist.

Functional and regression testing. Verifying that features meet their requirements, and that this release did not break what last release fixed.

API testing. Working directly against endpoints in Postman: contract validation, authentication and authorisation, input validation, error handling, and idempotency on repeated requests.

Database testing. Verifying stored state in SQL rather than trusting the interface. This is the skill he considers most underrated in manual QA.

Permission and role testing. Systematically checking every role against every action, including the combinations nobody designed for.

Mobile application testing. Across iOS and Android, including the device and OS-version variation that desktop testing does not have to think about.

User acceptance testing. Running UAT sessions with client stakeholders before go-live — as much a coordination skill as a testing one.

Tools

Jira — defect tracking, backlog grooming, sprint planning, and release scheduling. Both halves of his role run through it.

Postman — API testing, environment-per-role collections, assertions in the Tests tab, and saved negative cases that re-run every release.

SQL, across three engines — PostgreSQL and MongoDB at NIB Tech, MS SQL Server at QuaidSoft. Reading a schema, writing joins, and hunting for records that should not exist: cancelled bookings still holding captured payments, or order totals that disagree with the sum of their line items.

Selenium WebDriver with Java — certified in 2024. Element location, script structure, and automation fundamentals. He is candid that automation is a growing area for him rather than his deepest one.

Platforms he has tested on

• Next.js and React web applications
• React Native mobile applications
• PowerBuilder enterprise ERP — older, and instructive precisely because it is
• Web, mobile, and ERP, from consumer eCommerce to internal business systems

Testing across that range matters because failure modes differ. An ERP fails by quietly corrupting a number that surfaces in a report weeks later. A booking app fails under concurrency, when two people want the same slot.

Domain knowledge

Accumulated rather than certified, and often what makes the difference:

• Booking and reservation systems — availability, double-booking, cancellation windows, refunds
• eCommerce — carts, discounts, totals, order state
• ERP and CRM — cross-module data integrity, where a change in one screen surfaces as a wrong number three modules away
• Payments — the states a transaction moves through and what should be true at each

The non-technical half

Easy to skip and hard to replace: writing a defect report a developer can act on without a follow-up conversation, documenting what was tested and what was not, and being able to hold a release while explaining why in terms a business stakeholder accepts.

Depth versus breadth, honestly

The list above is broad, so it is worth marking where the depth actually sits.

Deepest — manual and exploratory testing, API testing in Postman, and database verification in SQL. Daily work, and has been for four years.

Solid — permission and role testing, regression strategy, defect management, UAT coordination, mobile testing.

Growing — test automation. Certified in Selenium with Java and used where it pays back, but he would not describe himself as an automation specialist today.

Not claimed — performance engineering, load testing, and security auditing as specialisms.

Setting that out plainly is not modesty. A QA engineer who claims every skill on the list is exactly the one you cannot trust about the ones that matter.

Languages

English, Urdu, and Punjabi.

The full toolkit is on the skills page, the products on projects, and his qualifications on the education page.