FAQ

Lynqa is currently in beta, which means the product may have some issues and will evolve quickly.

Whether to ask us a question, report a bug, or give 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:

• generate and manage your API keys

• purchase and track your credit consumption

• view the history of your tests

To learn more, visit this page

The Lynqa dashboard is the entry point to generate Lynqa API keys necessary for configuring the Jira app. It also allows you to manage your API keys, purchase and track your credits, view your test history. Visit here to see how to generate your Lynqa API key.

Only data contained in the action and expected result columns of manual tests are 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, it will not be accessible to Lynqa

A test can be in the “error” status. This happens notably 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 necessary for test execution 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 do not see your execution sessions, it is possible that the service is temporarily unavailable: in this case, just wait a few minutes and try again. Another case is when multiple API keys (from different accounts) are used. For more details, visit this page.

If your sessions remain inaccessible, you can contact us for help: https://lynqa.atlassian.net/servicedesk/

Lynqa is currently in beta, and we are aware that its performance can still be optimized. Our development and research teams are actively working to improve the agent's speed.

Lynqa is currently in Beta, and we are aware that its reliability in test execution can still be improved. Currently, reliability ranges from about 50% in the most complex scenarios to 75% in the best conditions. Our goal is to eventually achieve an average reliability above 90%.

Note: These results come from an internal benchmark designed to push our agent into deliberately complex situations. Therefore, they do not reflect real usage observed in production. To continue improving Lynqa, we invite you to participate in our research program by allowing the collection of your execution data in our benchmark.
This will allow us to identify difficulties more quickly and optimize the agent accordingly.

You can track credit consumption from Jira where the number of remaining credits is displayed. For finer management by API key, you must go to the dashboard.

One executed test = one credit. If a technical error occurs during execution, no credit will be consumed. If you observe 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

Each execution deducts credits from the same Lynqa account, regardless of the key used.

As soon as Lynqa has accessed the test URL, a credit is consumed. (Except when the service is unavailable, in which case the credit is refunded).

Lynqa API keys allow Jira users to use Lynqa's test execution service. Each key tracks test execution sessions. These keys are configurable by space and by user in the Lynqa app configuration. All users without a personal key will use the space key. For these users, it will not be possible to distinguish their individual Lynqa usage, as 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 Lynqa account. Then, you can distribute these keys by space and by user in the Lynqa app configuration.

Each account has its own API keys and its own execution sessions. In Jira, a user only sees executions linked to Lynqa API keys for a single account. We therefore advise avoiding creating multiple accounts with multiple keys for the same Jira space to facilitate consultation of execution sessions.

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