Software quality engineering · Riyadh

Quality is not
a choice — it's a mindset.

Mutqan Soft is a Saudi software quality engineering company. We test web, mobile and API products, automate regression, measure performance and security — and hand engineering teams evidence, not impressions, before every release.

  • Web
  • Mobile
  • API
  • Performance
  • Security
A sample of one quality cycle: requirement, test, defect found, analysis, fix, verification, release.
Every step carries its evidence: request, response, environment, screenshot.
01About

We know the difference between “it works” and “it’s ready”.

Mutqan Soft is a Saudi software testing and quality assurance company based in Riyadh. It was founded by test engineers who worked inside product teams and know how defects reach production — and how they are kept out.

We are not a coordination agency or an intermediary: the engineer who tests your product writes the defect report and verifies the fix. Four principles run through everything we do:

Evidence before opinionEvery defect ships with reproduction steps, environment, data and a recording — never “something seems off”.
Risk-based coverageWe start with what costs the most when it breaks — payment, sign-in, data — not with a generic checklist.
Testing at the right layerAPIs before the UI, automation for regression, manual testing where human judgement is needed.
Inside your environmentWe work in your repository, your tracker and your CI pipeline, at the cadence of your releases.
"Every defect that reaches an end user costs more than a technical fix — it costs client trust, brand reputation and opportunities that may not come back."
Mutqan Soft team — 2026
02Services

One quality system, six parts.

Pick a part to see what we actually do in it and what you receive at the end. The parts work together and are bought separately.

Manual testing

Functional and exploratory testing led by engineers who know where defects hide: critical paths, edge cases, and compatibility across devices and browsers.

What we do

  • Functional testing built from requirements and user stories
  • Exploratory sessions on the critical paths
  • Browser, device and OS compatibility
  • Pre-release acceptance testing

What you get

  • Documented, re-runnable test cases
  • Defect reports with reproduction steps and evidence
  • A coverage report and a clear readiness call

Test automation

An automated regression suite that runs on every change in your CI pipeline, so breakage is found in minutes instead of by a user days later.

What we do

  • API, web and mobile automation (Selenium, Cypress, Appium)
  • Framework, test data and environment setup
  • Execution wired into GitLab CI with a report per build
  • Suite maintenance and flaky-test triage

What you get

  • A regression suite you own outright, in your repository
  • Results on every change, with run history
  • A maintenance and hand-over plan for your team

Performance & security testing

We measure how the product behaves under real load and against common exploitation attempts — in numbers, before thousands of users measure it on launch day.

What we do

  • Load, stress and soak testing (JMeter)
  • Bottleneck analysis across services and databases
  • Checks for common OWASP weaknesses in web and API
  • Review of authentication, authorisation and input handling

What you get

  • Latency, throughput and error-rate metrics
  • Findings ranked by severity with reproduction steps
  • Fix recommendations and a re-measurement afterwards

Building QA teams

We help you build an in-house quality team that outlasts our engagement: clear roles, hiring based on practical exercises, and training on your own product.

What we do

  • Team structure, roles and the ratio to development teams
  • Interviews and practical assessments for candidates
  • Hands-on training in manual testing and automation
  • Coaching through the first two release cycles

What you get

  • Role descriptions and a ready hiring track
  • A team working to a documented methodology
  • A growth plan with metrics to follow

Quality system building

A written, working methodology: when what gets tested, what stops a release, and how improvement is measured — so quality becomes a daily habit rather than a seasonal campaign.

What we do

  • Assessment of the current process from requirement to release
  • Entry and exit criteria and release gates
  • Test management and traceability setup (TestRail)
  • Measurable quality indicators, reviewed regularly

What you get

  • A documented quality policy and working procedures
  • Templates for planning, execution and reporting
  • A dashboard of indicators to follow the trend

Enterprise consulting

An independent assessment of the current quality level of your product or portfolio, with a practical roadmap ordered by impact and cost — not a generic slide deck.

What we do

  • Review of existing tests, coverage and automation
  • Analysis of production incidents and their root causes
  • Readiness assessment before a major launch
  • Support for build-or-buy and vendor decisions

What you get

  • An assessment report with findings ranked by severity
  • A phased roadmap with effort estimates
  • A walkthrough session with your technical team
03How we work

From requirement to release, with evidence at every stage.

Six stages, each with a concrete output you receive. A stage is not closed until its output exists.

  1. 01

    Discover

    We read the requirements, the architecture and the defect history, and work out what costs the most if it breaks.

    Risk map
  2. 02

    Model

    We design the coverage: what is tested manually and what is automated, at which layer, with which data.

    Test strategy
  3. 03

    Test

    Manual and automated testing on an agreed environment, with every run and its result recorded.

    Execution logs
  4. 04

    Report

    Every defect with its severity, reproduction steps and evidence, in the tracker your team already uses.

    Defect reports
  5. 05

    Verify

    We re-test every fix and run regression so the defect cannot come back through another door.

    Regression results
  6. 06

    Release

    A written readiness decision: what was tested, what remains open, and which risks are accepted.

    Release decision
04Technologies

Tools we know well, one for each layer.

We choose the tool by what is being tested, and work with what your team already uses when it exists.

Web & mobile UI
SeleniumCypressAppium
API
Postman
Performance
JMeter
CI/CD & environments
GitLab CIDocker
Test management
TestRail
Automation languages
PythonJavaScript

On a different stack? We work with the test frameworks you already have before proposing others.

05Mutqan Tools

A tool platform we use ourselves, free for everyone.

Hundreds of tools for developers and test engineers, from the same team: formatting and validation, API testing, test data and test case generation, requirement and bug analysis, document processing, and internet, DNS and website diagnostics. Most run entirely in your browser — your data never leaves your machine.

The same tools we use in our own engagements. A free account saves favourites, downloads files and runs the AI tools; a tool that needs you to sign in asks before it runs.

Open Mutqan Tools
06Sectors

Where a defect is expensive.

The sectors we work in, and what actually gets tested there. We do not show client logos that cannot be verified publicly.

  • 01

    Fintech

    Payments, digital banking, wallets: calculation accuracy, transaction failure modes, and compliance.

  • 02

    Government

    Digital services and public platforms: accessibility, seasonal peak load, and integration with national systems.

  • 03

    Healthcare

    Care applications and patient systems: data integrity, permissions, and booking and results journeys.

  • 04

    E-commerce

    Cart, checkout and orders: discounts, taxes and shipping, and device compatibility at peak season.

  • 05

    Logistics

    Operations, delivery and tracking: system integrations, concurrent states, and time and location accuracy.

  • 06

    SaaS & education platforms

    SaaS products and learning platforms: multi-tenant APIs, roles and permissions, and performance under growth.

07Company profile

The Mutqan Soft company profile

Download the official Mutqan Soft company profile for a full overview of our software testing and quality assurance services — manual and automated testing, QA automation, performance and security testing, and the AI solutions and digital transformation work we deliver for clients across Saudi Arabia and the Gulf. Available as a direct download in Arabic, English and Hindi.

  • العربية

    The Arabic edition of the profile — for clients and government entities inside the Kingdom.

    Download PDF
  • English

    The English edition of the profile — for international partners and clients.

    Download PDF
  • हिन्दी

    The Hindi edition of the profile — for Hindi-speaking teams and partners.

    Download PDF

All three editions carry identical content, updated for 2026. Nothing is downloaded when the page loads — the file is requested only when you choose a language.

08FAQ

What a technical team usually asks.

Yes. Functional, exploratory, API and performance testing run against a test or staging environment without the code. Repository access helps with root-cause analysis and automation, but it is not a precondition for starting.

Yes. We start by reviewing the existing manual cases, rank them by value and how often they run, then automate what deserves automation at the right layer (API or UI). The suite is built in your repository, in your language and tooling, and stays yours.

Yes, and it is a common setup. We agree a clear split of responsibilities — for example we take performance and automation while your team focuses on functional testing — and work in the same tracker with the same methodology. If you want, we train the team on what we build so they can own it later.

Yes, and we prefer it. We test from the contract (OpenAPI or a Postman collection): valid and invalid cases, authentication, limits and performance. By the time the frontend arrives the service layer is trusted, and UI testing is shorter and sharper.

Yes. Automated suites are built to run in your pipeline (GitLab CI and Docker are part of our stack), with a result per build and agreed release gates: what blocks a merge and what is only reported.

It is reported immediately — not in the end-of-week report — with severity, reproduction steps, environment and evidence (request, response, recording). After the fix we re-verify on the new build and add the case to the regression suite so it cannot return.

Functional, API and performance testing do not depend on your product’s language. Automation we build to fit your team — usually Python or JavaScript — with tools such as Selenium, Cypress, Appium, Postman and JMeter, or with your existing framework when it fits.

We are based in Riyadh. We work on site in the Kingdom and remotely with clients across the Gulf and the region. Test documentation and reports are in Arabic or English, whichever your team uses, and Hindi is spoken within the team.
09Contact

Know what is ready before you release.

Talk to a test engineer

Tell us about the product, its stack and the release date. You will get a proposed test scope and an effort estimate back — not a sales pitch.

Send us the product details

Product, stack and release date — that is enough to start.

When you send this form, its contents are delivered to our mailbox through Web3Forms so we can reply; they are never sent to Google. Details: Privacy Policy