Managed QA

Delegate the QA. Keep the record.

From test plan review and exploratory QA to triage, retesting, and release memos, IXC experts perform the agreed QA scope on Qoretix. Results stay in the workspace shared with your team.

Talk about managed QARequest a demo

The platform records evidence and decisions. Experts handle the work that needs judgment.

Two ways to work

Delegate only what you need.

The platform stays the same. Only the responsibilities change.

A

Your team runs the platform

QA leads and testers prepare projects, approve cases, and review results and decisions themselves.

Your team's role

  • Connect repositories, target URLs, and test accounts
  • Approve case drafts from documents, code, and screens
  • Configure automation rules for pushes and PRs
  • Use decisions and evidence to decide on release

Best forTeams with in-house QA who want to define their own standards

Explore the platform

B

Experts work on Qoretix

IXC experts perform agreed QA work in the shared workspace. Review comments, exploratory findings, retest records, and release memos stay with the project.

What experts handle

  • Onboarding, QA setup, and test plan review
  • Pre-release exploratory QA and UX review
  • Failure triage and retesting
  • Release memo

Your team can handle case generation and execution, while experts handle pre-release exploratory QA and the release memo.

Best forTeams without QA staff, or those needing focused pre-release testing

Talk about managed QA

Combine both approaches and agree on scope during consultation.

Getting started

From consultation to your first release memo.

The first run typically takes five minutes to set up. Here is how the work around it proceeds.

  1. Scope consultation

    Agree on the project, release cadence, and work to delegate. After a mutual NDA, document the scope in a written services agreement.

    Customer owner · IXC

  2. QA workflow setup

    Experts help connect repositories and register URLs, test accounts, and requirements, then collect screens. Automation rules and approval flows are defined here too.

    Expert · QA lead

  3. Plan review and case approval

    Experts review the platform's plans and case drafts, remove assumptions not grounded in requirements, and add missing paths.

    Expert

  4. Execution and triage

    Automation runs on every push and PR. Experts triage failures, assign severity to reproducible defects, and record them in Jira. Unreproducible failures are deferred with a documented reason.

    Automation · Expert

  5. Exploratory QA and UX review

    Before release, experts explore screens and flows that automation has not opened. Review notes remain in the project, organized by screen.

    Expert

  6. Retesting and release memo

    Run the fixed commit again, verify the decision, and document what was tested and what remains. The customer owner makes the release decision.

    Expert · Customer owner

Execution, triage, exploratory QA, and retesting repeat with each release cycle.

Expert responsibilities

Eight tasks for human judgment.

Experts make the judgments automation cannot. Every result becomes a record on the platform.

Onboarding & QA setup

Set up projects, automation rules, roles, and approval flows to fit the team.

Test plan review

Compare plan rationale and selected cases with requirements to correct gaps and unnecessary scope.

Exploratory QA

Explore paths not covered by cases and document findings with reproduction steps.

Test maintenance

Fix cases when screens or APIs change, and approve or reject PR suggestions to keep the suite current.

Result triage

Distinguish defects, environment issues, and flaky behavior. Assign severity and record the reasoning in Jira.

UX review

Review screens across three browser engines with human eyes. Note interactions that work but are hard to use.

Retest

Rerun failed cases on the fixed commit and check whether the decision changes to PASS.

Release memo

Summarize the decision, coverage, remaining risks, and recommendations in one memo to support the release decision.

Records

Expert judgment leaves a record, too.

Keep it in the project, not scattered across chat or email. Plan comments, exploratory findings, triage rationale, and release memos live alongside execution history.

  • Plan review comments alongside plan versions
  • Exploratory findings with screens and reproduction steps
  • Triage rationale linked to failures and Jira issues
  • Release memos beside the decision card
View test reports & evidence

Frequently asked questions

Before you hand over the work.

What projects can we start with?
Web projects with staging URLs, test accounts, and a connectable GitHub repository are fastest to start. Server/API projects skip screen collection and begin with API testing.
How much access do experts have to our code and data?
Repositories are read through GitHub App permissions. Tests run only against registered staging URLs and test accounts. Access scope and retention periods are documented in the mutual NDA and written services agreement.
What does our team need to do?
Your owner provides requirements, approves cases, and decides on release. Other responsibilities are divided according to the agreed scope.
Is this useful if we already have a QA team?
Yes. Narrow the scope to pre-release exploratory QA or result triage, for example. Everyone works from the same workspace.
Who makes the release decision?
The platform issues its decision using defined rules. Experts do not override it; they add a release memo. The customer owner decides whether to release.
Can we keep our existing issue tracker and documents?
Connect Jira to create issues from failures and link them to results. Attach requirements as DOCX, XLSX, PPTX, PDF, images, or Markdown.

Managed QA inquiry

Let's decide what to delegate first.

Tell us about your project, release cycle, and team. We’ll help define the testing work and scope.

Managed QA inquiry

Briefly describe your timeline and the work you would like us to handle.

Request by email +82-33-242-0210