Integrations
Keep your tools. Add a release decision.
Pushes and PRs trigger tests. Failures become Jira issues. Security alerts inform release decisions. Add Qoretix to the repositories, issue trackers, and document formats your team already uses.
Repositories & pipelines Available now
From connection to first run,
typically five minutes.
Connect a repository through the GitHub App and register target URLs and test accounts. The platform identifies web, mobile, or server/API projects and sets the next steps. Server/API projects skip screen collection and go directly to API contract testing.
- Screen collection: browse the site while logged in and collect a screen inventory within 90 seconds.
- Automation rules: set repository, branch, and changed-path patterns to run on pushes and PRs, with an optional approval step.
- PR-based case suggestions: analyze changes and suggest new, updated, or removed cases for human approval.
- Run history and evidence are retained by commit, so you can trace where the decision changed.
Integration coverage
What connects to each tool.
GitHub, GitHub Actions, Jira, requirements documents, test accounts, and security alerts connect today. Explore other tools in preview.
| Area | Available now | Preview |
|---|---|---|
| Repositories & pipelines |
|
|
| Release gating |
|
|
| Issue tracking |
|
|
| Requirements documents |
|
|
| API specifications |
|
|
| Test account |
|
|
| Security testing |
|
|
| Production monitoring | — |
|
| Notifications |
|
|
| Public API | — |
|
Issue tracking & notifications Available now
Failures become issues. Decisions become notifications.
Failed cases automatically become Jira issues, with direct links to results, screenshots, replay videos, and logs. QA leads receive browser notifications when a decision becomes FAIL or a test is quarantined.
- Jira issues include severity (critical, major, minor, trivial) and links to results with evidence.
- When retesting passes, the issue's linked result updates, recording what was resolved.
- Six notifications: approval requests, run completion, FAIL decisions, quarantine, low coverage, and case suggestions
Technical foundations
What powers the integrations.
Whichever tools you connect, execution and decisions use the same engines and rules.
GitHub App connection
Connect individual repositories and receive push and PR events. PR changes feed case suggestions and automation rules.
Three browser engines
UI tests run separately on Chromium, Firefox, and WebKit. Quarantine is measured per engine, so instability in one engine does not distort the release decision.
API contract testing
Server/API projects validate contracts instead of screens. Response structures or statuses that differ from the contract are recorded as failures, with request and response logs as evidence.
Test accounts & target URLs
Log in with a staging URL and test account to collect screens. Attached permission matrices inform access-control test cases.
Dependency tree at each commit
Read the lockfile, check package versions against public vulnerability databases, and record dependencies at the tested commit. Packages reported as malicious are marked separately as critical.
Organization workspaces
Workspaces are separated by organization, so clients see only their projects. Three roles—QA lead, tester, and customer—use screens available in Korean, English, and Japanese.
Frequently asked questions
What to check before you start.
Can we use Qoretix with repositories outside GitHub?
How do we receive results without Jira?
We already use security and observability tools. Is this redundant?
Which requirements document formats are supported?
How are test accounts and target URLs used?
Can our pipeline trigger runs directly?
See a demo with your team's tools.
Tell us your repository, issue tracker, and document formats. We will show project setup through the first decision with that combination.
sales@qoretix.com+82-33-242-0210Weekdays, 10:00–18:00 KST