pylynqa
pylynqa is a Python client for the Lynqa REST API.
Lynqa is a test execution AI Agent: you describe a test (plain steps or a Gherkin scenario) and Lynqa runs it against your web application. This library provides a wrapper around the REST API, covering test run management, step inspection, screenshot retrieval, and organization operations.
Disclaimers
Requirements
- Python 3.9+
- A Lynqa account and API key (test executions consume credits)
Installation
pip install pylynqa
At this early stage the package may not be published on PyPI yet. In the meantime you can install it from source:
pip install git+https://github.com/petit-robot/pylynqa.git
Quick start
from pylynqa import CreateTestStep, LynqaClient
client = LynqaClient(api_key="your-api-key")
run_id = client.add_test_run(
url="https://lemonde.fr",
steps=[
CreateTestStep(
action="Go to the website",
expected_result="The website is open",
),
CreateTestStep(
action='Search an article on "france ia"',
expected_result='Should have an article on "IA agentique"',
),
],
name="Smoke - Search an article",
)
status = client.get_test_run_status(run_id)
print(status["status"]) # e.g. "running"
Bruno Collection
The project provides a Bruno Collection to interact with Lynqa API. A Bruno environment named "production" was also provided in addition to the collection.
You can access the collection here.
Prerequisites
Before using this collection, make sure you have:
- Bruno 3.4.2+
- A valid Lynqa API Key that you get once you have a Lynqa account
Where to put your API Key
To securely use the API, you must configure your API key inside a Bruno environment.
For that you should:
- Select the environment named "production".
- Click on "Configure" to get access to the environment variable
In the environment variable:
- Paste your Lynqa API Key in the Value field
- Make sure to mark it as Secret (enable the checkbox)
- Click Save
This ensures your API key is never exposed in Bruno files.
Collaboration
This project is at an early stage, so external contributions are limited for now. This may be opened up more broadly later as the project matures.
In the meantime, you are very welcome to open an issue to report a bug or ask any question.
License
Licensed under the Apache License 2.0.
Metadata
Release files for pylynqa 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pylynqa-1.0.0.tar.gz | 68.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pylynqa-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 103.7 kB
Release files / pylynqa-1.0.0.tar.gz
| Download URL | pylynqa-1.0.0.tar.gz |
|---|---|
| Size | 68.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa5d660bc1381893789736f16a9cfc72a865c20f769675bbc4f230f8f903d085
|
|
BLAKE2b-256 checksum How to use checksums |
e625910e8fd370e23dc26170cb655d7608e7e370393b793ff9eaa3b0eea557a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / pylynqa-1.0.0-py3-none-any.whl
| Download URL | pylynqa-1.0.0-py3-none-any.whl |
|---|---|
| Size | 34.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c336b4096ac28f7d903e2d30f3c70969dd40356cd39f110a407652718b89e6d1
|
|
BLAKE2b-256 checksum How to use checksums |
7c1202d59ea7c6714602cffabea045524f67262d7486d59e6b5679a7e1b32631
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logSecurity for pylynqa 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pylynqa-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.