TestMu AI Integration
Connect TestMu AI (the current product name for the LambdaTest automation platform) so TestRelic can use your TestMu AI Automation and App Automation account data for this organization. Credentials are org-wide; optional build filters and product choice are configured per repository.
What you configure in TestRelic
| Level | Where | What you set |
|---|---|---|
| Organization | Settings → Integrations | Username and access key |
| Repository | Repository detail → Integrations → Cloud Farms | Product, build tag filter, artifact caching |
Connect TestMu AI (organization)
- Open Settings → Integrations.
- Find the TestMu AI card and open Configure (or Connect if not yet connected).
- Enter:
- Username — Your TestMu AI account username (often your account email).
- Access Key — From the TestMu AI dashboard: Profile → Password & Security → Access Key.
- Save to verify the connection.
TestRelic’s in-app catalog links to LambdaTest’s published API documentation: LambdaTest API documentation. TestMu AI is the rebranded product; use your TestMu AI dashboard for the access key location above.
Per-repository: Cloud Farms
After TestMu AI is connected for the organization:
- Open the Repository you want to scope.
- Go to the Integrations tab.
- Open the Cloud Farms segment (it appears when TestMu AI or BrowserStack is connected at org level).
TestMu AI Build Filter panel
| Field | Purpose |
|---|---|
| Product | Automation (web) or App Automation (mobile). |
| Build tag | Optional substring. The in-app help states that only builds whose name contains this string are pulled for this repo; leave blank to show all builds. Example placeholder in the app: e.g. nightly for substring matching. |
| Cache videos / logs / screenshots to TestRelic storage | When enabled, artifacts are cached in TestRelic so the Session Workspace and Ask AI can still use them if TestMu AI is temporarily unreachable. |
Click Save to persist repository settings.
If TestMu AI is not connected under Settings → Integrations, the Cloud Farms area prompts you to connect there first; per-repo filters apply only after org-level credentials are valid.