Qodex

以下为收录时的原文，语言与页面不同，未做翻译。

Qodex is an automated API testing platform that streamlines test creation and execution, offering features like automated test generation, uptime monitoring, and real-time failure alerts, facilitating efficient testing in CI/CD workflows for developers and QA teams.

官网介绍

Qodex turns test knowledge into durable scenarios that evolve with your product and run in GitHub pull requests, the CLI, chat, schedules, and deploy checks.

官网要点

• API security testing
• Uptime monitoring

官方常见问题

How is this different from an AI code reviewer or bug bot?

Code reviewers read the diff and guess. Qodex runs your scenarios against the real running app, then shows what actually broke. One reads, the other runs. Try both for a sprint and compare what each one catches.

Does Qodex change our code, merge, or deploy on its own?

No. It posts findings and status checks on your pull requests, and a human decides what merges. When a test goes stale it proposes the repair as a diff for you to approve.

What access does Qodex need, and what happens to our code and data?

The app requests read access to your pull requests, not write access to your source. Data is encrypted in transit and at rest on servers in the United States, isolated per project, never sold, and never used to train models.

How are our credentials handled, and what do model providers see?

Environment tokens are cached for thirty minutes, cleared when you save an environment, and redacted in API responses. Bring your own model key if you prefer; every call is logged, provider agreements exclude training on your data, and cached replays make no model call at all.

How long does setup take, and what do we have to install?

Install the GitHub app on the repositories you choose and point Qodex at a preview or staging URL. Nothing goes into your application, no runner goes into your CI, and no existing test has to be rewritten. The next pull request gets reviewed.

Do we need a preview environment?

Qodex runs scenarios against a URL: a per-PR preview deploy if you have one, otherwise a shared staging environment. API scenarios need the API reachable; UI scenarios need the app reachable in a browser.