API
API testing
Short answer
API testing at QA Patrol is REST testing for products that have, or are growing, a mobile or web client. Mate Ajduković has done it with Python and Postman at Matchbook and with Java at Ericsson. The API tools on the site are Postman, REST Assured, and curl. The site documents REST, and does not describe GraphQL, gRPC, contract testing, or load testing.
What API testing covers here
- Backend REST API testing with Python and Postman at Matchbook, next to the Appium mobile suite, from October 2017 to April 2020.
- Backend REST API testing in Java at Ericsson, on the HDS8000 data center platform, from June 2015 to June 2017, alongside Selenium web tests.
- A Dockerized QA repo at Matchbook, with tests on real devices via BrowserStack. The API checks lived in that same automation project.
- Postman, REST Assured, and curl, which are the API row of the public tool list. REST Assured is listed as a tool. The project write-ups do not name it on a specific client.
- API coverage inside Embedded QA, which already says mobile, web, and API testing, manual and automated.
API tools on the site
- Postman
- REST Assured
- curl
Where this shows up
Matchbook
Backend REST API testing with Python and Postman, in the same effort as the Appium and Python mobile framework. The QA repo was Dockerized. Jenkins is in that project’s stack.
↗Ericsson
Backend REST API testing in Java on HDS8000, with TestNG, Selenium, Jenkins, and TestLink also in the stack.
↗What this page does not add
The public project list talks about REST. It does not mention GraphQL, gRPC, consumer-driven contract tests, or performance and load testing. Those are not offered from this page.
If the risk is in the API and the team wants someone in the sprint, that is Embedded QA. If the need is a process and tool decision first, that is QA Consulting: audit, strategy, tool selection, and ongoing advisory.
How an engagement runs
A testing engagement uses one of the four shapes already published on QA Patrol. The site does not add a separate delivery timeline on top of these.
- Embedded QA, marked most popular: full-time, part-time, or hourly. Joins standups, sprint planning, and retros, and works the backlog. Mobile, web, and API, manual and automated.
- QA Consulting, listed as custom: process audit and review, strategy and roadmap, tool selection, and ongoing advisory.
- Team Training, listed as custom: workshop content for that team, hands-on exercises, real-world scenarios, and follow-up support.
- 1-on-1 Mentoring, listed as “Let’s talk”: career guidance, test automation coaching, interview preparation, and flexible scheduling.
- The contract is direct, or through an EOR such as Deel or Remote.com.
Pricing
Hourly QA is $40. A one-off QA audit (about 20 hours, findings report) is from $800. Test automation setup (about 60 hours, framework and first suites) is from $2,400. Fractional QA is from $1,600 a month at about 10 hours a week, or from $3,200 a month at about 20 hours a week. “From” prices depend on the final scope.
The full list is on the pricing page, in US dollars. The Croatian page lists euro prices, which are set amounts, not a conversion. Companies hire Mate directly as a contractor or via an employer of record (Deel, Remote.com, and similar).
Questions
Which API tools do you use?
Postman, REST Assured, and curl. On named projects: Python and Postman at Matchbook, and Java for REST at Ericsson.
Do you test APIs in code, or only in Postman?
Both appear on the site. Matchbook used Python and Postman. Ericsson’s REST testing was in Java. Postman, REST Assured, and curl are all on the tool list.
Do you test GraphQL?
The site does not say so. Documented API work is REST, at Matchbook and Ericsson.
Can API testing be part of an embedded engagement?
Yes. Embedded QA lists mobile, web, and API testing, manual and automated, inside the team’s standups, planning, and retros.
Is there a fixed price for an API test pass?
There is no separate fixed price for an API pass. Hourly QA is $40. A one-off audit is from $800. The full list is on the pricing page, and “from” prices follow the final scope.
API
Tell me where the risk is.
The intro call on this site is 30 minutes. Bring the product, the release pressure, and the quality risk you actually have.