Frequently asked questions

The short version of the questions teams usually ask before bringing a workflow to QTXpert.

About the workflow

What can I bring into QTXpert?

A URL or app flow, API contract, requirements document, user story, acceptance criteria, Jira or Confluence context, video, screenshots, or a plain-language description.

What does QTXpert produce?

It helps turn context into an understandable quality model, editable test coverage, governed execution, and evidence for review.

Are generated tests editable?

Yes. Teams should review and refine priorities, preconditions, steps, and expected results before relying on a suite.

About Autopilot

What is QTXpert Autopilot?

Autopilot is the autonomous testing layer. It runs approved coverage across connected environments and captures status and evidence within the controls configured for the workflow.

Does Autopilot make release decisions?

No. People remain accountable for scope, approvals, exceptions, and release decisions.

What happens when something is unclear?

A governed workflow should pause, flag the exception, or follow the configured failure policy rather than silently treating uncertainty as success.

About access and help

Can I see a real product flow?

Yes. The product demo shows sample workspace data and the quality loop in context.

How do I get help with a real project?

Use the request a walkthrough flow. A QTXpert specialist will contact you by email to understand your needs and discuss the right solution.