Automation

Test automation

Short answer

Test automation at QA Patrol is framework work and day-to-day automated checks for startups, across mobile, web, and APIs. Mate Ajduković has built a mobile framework from scratch in Appium and Python (Matchbook), maintained a Cypress web suite (Carb Manager), and automated Android and iOS with Espresso and XCUITest (Numbrs) and with Appium and Kotlin Multiplatform (Waves Labs). Maestro is the tool on FrontRow and in the Breeze stack.

Automation the site already names

  • Mobile, from zero: Matchbook, Appium and Python for iOS and Android, Docker, Jenkins, BrowserStack, real devices in CI.
  • Mobile, in a product team: Waves Labs, Appium and Kotlin Multiplatform on BrowserStack, with Claude Code used daily for test design, reproduction, and debugging.
  • Mobile, native frameworks: Numbrs, Espresso for Android and XCUITest for iOS, in Java.
  • Web: Carb Manager, JavaScript and Cypress, built and maintained. Selenium in Java at Ericsson and BetBright. Playwright on the tool list and the Toptal stack.
  • API: Python and Postman at Matchbook, Java REST at Ericsson. Postman, REST Assured, and curl on the tool list.
  • CI and devices named in those stacks: Jenkins, GitHub Actions (FrontRow), Docker, BrowserStack.
  • AI-assisted QA, as the homepage states it: Claude Code, Cursor, and LLM evals, with Gemini also on the tool list. Job Radar is his personal project for LLM evaluation, not a client testing result.

Automation tools on the site

Mobile, web, and API rows, plus the CI tools those projects list.

  • Appium
  • Maestro
  • Espresso
  • XCUITest
  • BrowserStack
  • Cypress
  • Selenium
  • Playwright
  • Postman
  • REST Assured
  • curl
  • Jenkins
  • GitHub Actions
  • Docker

Frameworks tied to a name

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

Can you build an automation framework from scratch?

Yes. Matchbook’s write-up says the mobile QA automation project was built from scratch in Appium and Python, then Dockerized and run on real devices through BrowserStack.

Do you use Maestro?

Yes. Maestro is on the mobile tool list. FrontRow uses Maestro flows and GitHub Actions. Breeze, Mate’s own app, lists Maestro in its stack.

What CI do you plug tests into?

Jenkins is in the stacks for Matchbook, Numbrs, Ericsson, and BetBright. GitHub Actions is named on FrontRow. Docker is named on Matchbook. The site does not claim a single mandatory CI product.

Do you use AI in the QA workflow?

The homepage says he works with startups on AI-assisted QA workflows using Claude Code, Cursor, and LLM evals. Waves Labs names Claude Code for test design, bug reproduction, and debugging. Gemini is on the tool list. That is the claim. There is no published accuracy score.

Will you maintain a suite someone else started?

Carb Manager says he built and maintained the Cypress suite, and the role included mentoring testers. Embedded QA is the shape for ongoing ownership: full-time, part-time, or hourly, inside the team’s sprint.

Automation

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.