Ask Qualium Copilot
Open Copilot from the top header to ask grounded questions about repository code, staging discovery, runs, findings, reports, fixes, or Qualium APIs.
Go to this area →Help Center
Practical guidance for connecting, testing, reviewing, and safely improving your application.
How Qualium works
Qualium combines repository understanding with controlled staging exploration. It discovers the product, plans risk-driven coverage, executes specialists, independently reproduces candidate defects, and produces an explainable release verdict.
Connect an application
Paste a GitHub URL and HTTPS staging URL. For a private repository, use Connect with GitHub or a short-lived fine-grained token limited to that repository.
Go to this area →Credentials and tokens
Use disposable staging credentials and repository-scoped tokens. Qualium encrypts them at rest, supplies them only to scoped workers, and never displays them again.
Go to this area →Run autonomous QA
After discovery, start a Full QA run from Overview or Test Runs. Qualium selects specialists according to architecture, journeys, history, and risk.
Go to this area →Review findings
Open Issues to inspect independent reproduction, evidence, expected versus observed behavior, business impact, and likely root cause.
Go to this area →Understand verdicts
PASS has no confirmed release blockers in tested coverage. PASS WITH RISK has material uncertainty or non-blocking findings. BLOCK has confirmed critical or high-risk defects.
Go to this area →Autonomous fixes
Confirm a finding before requesting a fix. Qualium works in an isolated branch, verifies the patch, and opens a pull request for human review; it never merges to the default branch.
Go to this area →Frequently asked questions
Can Qualium test a private repository?
Yes. Use the official GitHub authorization flow when configured, or provide a fine-grained PAT limited to the selected repository.
Should I connect production?
No. Use an isolated HTTPS staging environment containing representative test data and sandboxed external integrations.
Will Qualium modify my main branch?
No. Testing is read-only. Requested fixes use a protected Qualium branch and require human pull-request review and merge.
Where are credentials stored?
Repository and staging credentials are encrypted with separate production keys. Plaintext values are not returned to the UI or written to reports and evidence.
What should I do with a false positive?
Reject it from Issues. Qualium records codebase-scoped feedback so similar future observations can be suppressed or interpreted correctly.