Executes your tests directly from Xray, with no adaptation
Sends step-by-step results and execution evidence back to Xray

for
Execute your Xray tests automatically with AI
Lynqa for Xray (Jira Cloud) executes your tests directly from Xray and sends step-by-step reports and evidence back to Xray in one click.
No scripts to create or maintain. No test rewriting.
no card required
10 free credits
ready in <5 min
Install → Connect → Execute
Install Lynqa from Marketplace, create & connect your account, and launch execution from Xray in a couple of clicks.
Run tests in parallel for greater scale
Launch your existing tests unchanged
Cut manual QA spend from €0.89/test
Lynqa works where your tests already live
Native Jira Cloud + Xray integration
How Lynqa works
Lynqa executes the steps → You review and validate
Lynqa reads your natural-language steps and performs the actions in your application (navigation, clicks, inputs, etc.), while capturing evidence along the way.
They trust us
“Lynqa is an excellent tool for executing manual tests, including end-to-end scenarios. We deliberately put it to the test using poorly or insufficiently documented test cases, sometimes incomplete. Despite these challenges, Lynqa was able to execute them successfully and provide actionable results.”
Uses Lynqa for Xray
What you get
Speed up execution across your Xray workflow
Manual execution slows releases down, and test automation alone can’t cover every scenario or every team need.
Lynqa enhances your Xray workflow.
Not every Xray test case belongs in scripted automation
Use Lynqa for flexible execution in Xray. Keep scripts for stable CI/CD regression.
| When... | Lynqa is the best choice | Scripted automation is the best choice |
|---|---|---|
| the flow is still evolving and needs flexibility | ||
| you want fast automation without writing or maintaining scripts | ||
| functional QA teams need to automate directly from test scenarios | ||
| the value comes from accelerating execution and reducing manual effort | ||
| the flow is stable and part of a long-term regression suite | ||
| tests must run on every build in CI/CD |
Use Lynqa for flexible Xray coverage, and scripts only for fixed regression checks.
Built for Oversight & Confidence
Human review
Lynqa follows the defined paths; you validate the result.
Security
Web apps covered
Mobile and desktop applications coming soon.
Performance
Lynqa runs outside Xray so it doesn’t slow down Jira.
Not on Xray?
You can still use Lynqa on its own or integrate it with other tools like SquashTM or XQual.
We Answer Your Questions
How does it work with Xray (Jira Cloud)?
You select the tests in Xray and start a Lynqa execution session. Lynqa executes the steps on your application, and you receive structured results and evidence that you can choose to save in Xray or not.
What are the prerequisites to run Lynqa for Xray?
You’ll need:
- Jira Cloud with Xray installed
- Admin rights to install the app from the Atlassian Marketplace and generate the Xray API key required for Lynqa configuration.
- A Lynqa account with credits available to run tests
Operational prerequisites:
- The target application must be reachable from Lynqa’s execution environment (public URL by default, or private access with the right setup: contact us in this case)
Test quality expectations:
- Keep steps clear and actionable, with expected results that can be checked. They should not rely on implicit domain knowledge or assumptions.
What do I get after a run?
A clean, reviewable execution trail:
- Step-by-step actions
- Screenshots and evidence along the way
- A clear verdict per step (not just a final pass/fail)
What happens if a UI changes? Do we need to rewrite tests?
You do not rewrite tests. Lynqa runs your tests as written and it can handle UI changes.
If a UI change breaks a step, the execution may stop (because your verification focuses on a specific element of the UI) and the report will show where it failed with the evidence captured so far. You usually update the affected steps the same way you would in manual testing, then rerun.
How are credits consumed?
One test execution consumes one credit. If a technical error occurs during execution, no credit will be consumed.

Our selection of Lynqa content
Discover our latest innovations and premium content made for you — software quality professionals!







