FAQ

Whether you want to ask us a question, report a bug, or send us feedback, you can use our service desk to contact us: https://lynqa.atlassian.net/servicedesk/

The Lynqa dashboard is an application that allows you to:

• manage your organizations

• generate and manage your API keys

• purchase and track your credit consumption

• view your test history

To learn more, go to this page

My Lynqa is the entry point for generating the Lynqa API keys required to configure the Jira app. It also lets you manage your API keys, purchase and track your credits, and view your test history. Go here to see how to generate your Lynqa API key.

Only the data contained in the action and expected result columns of manual tests is currently supported.

• Make sure the provided URL is publicly accessible, as Lynqa servers must be able to access it

• If the URL is behind a firewall or VPN, Lynqa will not be able to access it

A test may have the “in error” status. This can happen in particular when:

• The tests request elements that do not exist or cannot be found in the application.

• The test conditions are contradictory or impossible to satisfy.

• Resources required to run the test are unavailable.

In these cases, a clear error message is displayed to explain the cause.
If you do not understand the displayed message or if it seems incorrect, you can contact us for help: https://lynqa.atlassian.net/servicedesk/

If you cannot see your execution sessions, the service may be temporarily unavailable: in that case, simply wait a few minutes and try again. Another possible case is when multiple API keys from different organizations are being used. For more details, see this page.
If your sessions remain inaccessible, you can contact us for help: https://lynqa.atlassian.net/servicedesk/

Lynqa continues to evolve, and its performance is constantly improving. Our development and research teams are actively working to optimize the agent’s speed and efficiency in order to ensure an increasingly smooth experience.

Lynqa is constantly evolving, and we are actively continuing to improve its reliability when running tests. Today, reliability ranges from approximately 50% in the most complex scenarios to 75% under optimal conditions. Our goal is to eventually reach and maintain an average reliability above 90%.

Note: these figures come from an internal benchmark designed to push our agent into deliberately complex situations. They therefore do not reflect real-world usage observed in production. To continue improving Lynqa, we invite you to participate in our research program by allowing your execution data to be collected in our benchmark.
This will help us identify the difficulties encountered more quickly and optimize the agent accordingly.

You can track credit consumption from Jira, where the number of remaining credits is displayed. For a more detailed understanding of your consumption, please go to My Lynqa.

One test run = one credit. A credit is consumed once Lynqa accesses the URL. If a technical error prevents a status from being set on at least one test step, the test is considered “not launched” and no credit is consumed. If you notice abnormal credit consumption, you can contact us via our service desk: https://lynqa.atlassian.net/servicedesk/

Visit the Lynqa dashboard at https://my.lynqa.smartesting.com to check your credit balance and purchase additional credits if needed. You must be an administrator of your organization to purchase credits.

Each execution deducts credits from the organization that owns the API key used.

Once Lynqa has been able to access the test URL, a credit is consumed. (Except when the service is unavailable; in that case, the credit is refunded).

Lynqa API keys allow Jira users to use Lynqa’s test execution service. Each key makes it possible to track test execution sessions. These keys can be configured by space and by user in the Jira app configuration. Any user who does not have a personal key will use the space key. For these users, it will not be possible to distinguish their individual Lynqa usage, because all executions will be grouped under the same space key.

You can create as many keys as you want; they will all be linked to your organization. You can then assign these keys by space and by user in the Lynqa app configuration.

Yes, but for all users who use the same key, it will not be possible to distinguish their individual Lynqa usage, because all executions will be grouped under the same API key.