Projects · Customer workspaces Available now

Each organization sees its own projects.

Separate workspaces by client and project. QA lead, tester, and client roles define who configures, executes, and makes release decisions. Agencies and integrators can give each client direct access to their results.

Request a demo Implementation consultation

Korean, English, and Japanese interfaces

Set up the project Available now

From repository connection
to first run in about five minutes.

Connect a GitHub repository, register a target URL and test accounts, and your project is ready. Qoretix detects web, Android, iOS, macOS, Windows, or server/API projects. Server/API projects skip screen collection and go straight to API validation.

Connect repositories through the GitHub App. Staging URLs are recommended
Screen collection: explore the site in up to 90 seconds to build an inventory for case generation
Requirements: attach feature lists, wireframes, WBS, and permission matrices as DOCX, XLSX, PPTX, PDF, images, or Markdown
Automation rules: set repository, branch, and changed-path patterns to run on pushes and PRs, with an optional approval step.

Explore test planning

Dashboard Available now

The most serious issues come first.

The workspace dashboard combines each project's latest release verdict, unresolved security and test findings, and validation scope. It is the first view for QA leads managing multiple projects.

Unresolved: combine security findings and failed checks, ordered by critical and major severity
Release verdicts: latest PASS, CONDITIONAL, or FAIL for each project
Setup progress and scope: projects, repositories, screens, cases, and runs
Recent runs: see commits, run types, and result counts, then open the report

More about test reports & evidence

Commerce web › DashboardKO

Commerce webStaging

Overview

DashboardQuality trends

Test preparation

ProjectChecklist

Test execution

Automation rulesRun history

Test results

ReportsCoverageTest reliability

Extensions

Security testingSupply chain · MalwareProduction monitoring

Dashboard

Start with what needs attentionRuns

Unresolved Security, supply chain findings, and failed tests

17items2 critical 4 major 7 minor 4 trivial

Release decision Latest run by project

Commerce webPASS
Partner portalCONDITIONAL
Settlement APIFAIL

Coverage Requirements · Checklist · Screens

83%Requirements

15/17Checklist

46/48Screens

Recent runs

Runs	Type	Commit	Result	Decision
#49	Retest	1c8e77a	47 passed · 1 skipped	PASS
#48	Pre-release	9f3c2e1	45 passed · 1 failed · 1 quarantined	CONDITIONAL
#46	Pre-release	5b21d90	1 critical security finding	FAIL

Roles

Three roles for setup, execution, and decisions.

Separate setup and approval, authoring and execution, and review and decisions. Managed QA experts join client workspaces as testers or QA leads.

QA leadConfigure · Approve · Sign off releasesManage project settings, automated execution rules, PR case approvals, and release sign-off.

TesterWrite · Execute · ReviewWrite and run cases, classify failures, rerun checks, and review Jira issues.

ClientView results · Decide on releasesRead reports, evidence, and verdicts to decide whether to release. Settings and cases cannot be changed.

Notifications and languages

Get notified when a decision is needed.

Browser notifications Available now

Six role-based notifications cover approval requests, completed runs, FAIL verdicts, quarantined checks, coverage shortfalls, and case suggestions.

Email, chat, and webhook notifications Preview

Receive the same six notification types by email, team chat, or webhook.

Korean, English, and Japanese UI Available now

Workspace screens and generated cases support Korean, English, and Japanese. International client projects can use the same workspace in their preferred language.

SSO login testing Preview

Include login through your organization's SSO in validation flows instead of a separate test account.

Frequently asked questions

Workspaces and onboarding.

Can an agency or integrator manage multiple clients from one account?

Create a workspace per client and add agency members as QA leads or testers. Client contacts see only their own workspace's results; other clients' projects do not appear in their lists.

Can clients see repositories or code?

Clients access only reports, evidence, and release verdicts. QA leads alone manage repository connections, automation rules, and test accounts. Testers and QA leads write and execute cases.

Where are test accounts and target URLs stored?

They are registered in project settings and cannot be accessed outside the workspace. We recommend staging test accounts rather than production accounts. Storage and processing details are in Deployment & data handling.

What role do Managed QA experts take?

Experts join as testers or QA leads according to the agreed scope. They review plans, perform exploratory QA, classify results, revalidate, and write release notes. Your team makes the release decision.

Can we use Qoretix with repositories outside GitHub?

GitHub repository connections and GitHub Actions triggers are available. Other repository hosts and CI integrations are in preview. PR case suggestions and security scanning require a repository connection; we agree on applicable scope during onboarding.

Can one project include both web and API checks?

Qoretix detects the platform: web projects use screen collection and UI validation, while server/API projects use contract validation. Web projects can also run API cases in the same release verdict.

Plan workspaces around your clients.

We will review project counts, roles, and repositories to agree on the right onboarding scope.