FAQ – Frequently Asked Questions and Help Guide

Lynqa is an AI agent that runs tests on the application’s GUI.

Lynqa can be used in several ways, depending on your setup:
With your test management tool (recommended)

• Jira Cloud / Xray users

Use the Lynqa for Jira app. It retrieves your Xray manual or Gherkin tests, executes them automatically, and synchronizes detailed, step-by-step reports back to Xray.

• XQual users
  Contact XQual to enable the Lynqa add-on (integration developed by a partner). You can run your XQual tests automatically with Lynqa, and results are synchronized back to XQual.
• Other tools
  Additional native integrations are coming soon. You can also use the Lynqa API for custom integrations.

A My Lynqa account is required in all cases to:

• Manage API keys
• Purchase credits

With My Lynqa (standalone platform)
Write or paste your manual tests in natural language, execute them directly from the platform, and review results without synchronization to a test management tool.

Via API (custom integration)
Integrate Lynqa into your own tools or workflows. Contact us to learn more.

Lynqa aims to accelerate manual testing cycles, serving QA teams. It offers the following benefits:

• Automated test execution without preparation
• No maintenance for scripted test code
• Always available
• Reduced cost of manual tests
• Scales through availability and parallel throughout

Classical test automation usually means turning tests into scripts (or recorded flows) that teams build, maintain, and debug as the product changes.

Lynqa is different: it automates the execution of your manual tests. You keep your test cases written in natural language or Gherkin (Gherkin is only supported by Lynqa for Xray at the moment), and Lynqa runs them and produces step-by-step evidence, without creating a separate scripted suite, without code or no-code. As your application evolves, Lynqa dynamically re-analyzes the interface and adapts.

Many “AI-assisted test automation” tools focus on creating automated tests (generate test scripts, record actions, self-heal locators, maintain flows).

Lynqa focuses on something else: running the manual tests you already have. There is no new automated suite to build, no change in how your team writes tests, and no parallel maintenance project to keep scripts alive. Lynqa executes and reports; your team validates.

No. Lynqa is designed to complement them.

Keep scripted automation for stable, frequently repeated paths where it pays off. Use Lynqa for the tests that remain manual because they change too often, aren’t worth scripting yet, or require strong evidence and traceability.

Typically:

• Unit tests
• Smoke checks (often non-functional)
• Stable regression journeys executed every iteration

Lynqa shines on system/functional tests for web applications, especially when:

• The feature is new or evolving
• The flow is too volatile to justify scripted automation
• You need consistent evidence for reviews, audits, or team alignment

Lynqa executes tests by carefully checking expected results and recording all execution evidence, rather than running a coded script.

Lynqa simulates human testing, interacting with the application and evaluating results in the same manner as a person. Consequently, individual test execution times are comparable to those of a human tester. However, Lynqa offers the advantage of running simultaneous tests.

Lynqa for Xray :
For the main integration, you’ll need:

• Jira Cloud with Xray installed
• Admin rights to install the app from the Atlassian Marketplace and generate Xray key API required for Lynqa configuration
• A My 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.

My Lynqa :

• A My Lynqa account with credits available to run tests (you get 10 free credits when you create your account)

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.

Yes. Launching executions requires a My Lynqa account and credits. You can create a Lynqa account here.
For Xray users you need to install the Lynqa application from the Atlassian Marketplace.

In other situations, you have the option to execute tests directly within my Lynqa or get in touch with us to discuss existing partner integrations and available possibilities.

No. Lynqa runs executions outside of your machine. Jira/Xray stays in your test repository and reporting space; Lynqa is the execution engine.

You select the tests in Xray, start a Lynqa execution session, Lynqa executes the steps on your application, and you get structured results and evidence that you can choose whether or not to save in Xray.

Yes, Lynqa can run tests in parallel. If the maximum parallel test execution capacity is reached, the tests are put on a waiting list and will start automatically as soon as an execution slot becomes available.

You can write tests in multiple languages (English, French, Spanish, German, etc.). Lynqa provides responses and reporting in the same language.

You get a report showing exactly where it got stuck, with the evidence captured so far. In practice, teams either:

• Adjust the test wording (if the step is not explicit enough)
• Fix environment data/access
• Rerun once the blocker is removed

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.

Today, Lynqa supports system/functional testing for web applications.

Mobile and desktop app coverage coming soon.

It depends on network access from the execution environment. If your application isn’t publicly reachable, you’ll typically need a setup that allows Lynqa to reach it safely. Contact us in this case.

Your team does. Lynqa executes and collects proof; testers keep the final word. That’s intentional: execution is automated, but quality ownership remains in human hands.

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)

There is a way to provide sensitive data (such as passwords) when launching tests. These values are not processed by the AI in order to keep them secret during execution.

Executions performed with Lynqa are stored for 30 days. During this period, you must therefore ensure that you save the execution results in your test management tool in order to store them for the longer term.

Executions run outside your machine, in Lynqa’s execution environment (hosted by Scaleway at their data center in France).

Lynqa for Xray: Results and evidence are written back into Xray at the user’s request.

My Lynqa: Results and evidence are stored on My Lynqa.

For more security information, visit our Trust Center.

Lynqa for Xray: If you use Jira Cloud and Xray, install from the Atlassian Marketplace, and you’ll get 10 free credits to try on your own test cases.

My Lynqa: If you are not an Xray user, you can use My Lynqa. You get 10 free credits to try on your own test cases.

Yes. You can use My Lynqa: create your account here and get 10 free credits to try it.

Lynqa is usage-based: 1 credit equals 1 test execution. Current packs start at €1/test (Pack 100) and go down to €0.89/test (Pack 2000), excluding VAT.

One test execution consumes one credit. If a technical error occurs during execution, no credit will be consumed.

Yes, contact us for more information.

Xray and Xqual are the first integrations. Lynqa is designed to expand to other test management tools progressively. Subscribe to the newsletter to be notified when your tool is supported.

We are committed to maintaining high standards of security and data protection. We are currently undergoing the SOC 2 process, and the most up-to-date information is available in our Trust Center.

Data Retention & Processing
Our approach to data handling is designed to ensure transparency, traceability, and customer control.

Test execution data
Includes steps, URLs, screenshots, and evidence generated during runs.

• Stored in Europe (FR).
• Retained for 30 days unless earlier deletion is requested.
• Screenshots of the SUT are stored in a non-anonymized form.

Sensitive data / PII

Customers are responsible for ensuring that no personal data or sensitive information is included in test data or test environments.
Screenshots and test inputs are processed as provided and are not automatically anonymized.

LLM processing
Screenshots and test data may transit through our LLM provider (Anthropic, US) strictly for test execution and reasoning purposes. These data are not used for model training.

All data is encrypted in transit and at rest, and access is restricted according to least-privilege principles.

For detailed and up-to-date security documentation, please refer to our Trust Center or contact security@smartesting.com.

If something goes wrong you can reach us in two ways:

• Use the dedicated support entry in Jira (Service Desk)
• Or contact our team directly at lynqa-support@smartesting.com