Nightly failures triaged
Sarah Chen, QA lead at Acme Ltd, asked which sessions failed in the nightly build. Memtro listed them with browser, platform and remark. She saw the failures were all on one browser version and raised it with the team.
LambdaTest + Memtro
Which LambdaTest sessions failed in the nightly build?
LambdaTest connects Memtro to your cloud testing account. It reads automation builds and test sessions with status, browser, platform, duration and remarks, and running and queued concurrency. It also reads open tunnels and Test Manager projects, folders, test cases and test runs with pass and fail counts. When asked and granted, it can mark sessions passed or failed, rename, stop or delete sessions and builds, stop tunnels, and create projects, test cases and runs, record results and archive or delete runs. Accounts on the EU data centre set the region, and usernames and session log links are never returned.
In Memtro
What you can do with LambdaTest in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right LambdaTest tool, reads what it needs, and answers with the source cited.
What it does
- 01Automation builds with status, project, tags and duration, and test sessions with status, remark, browser, platform and device.
- 02How many tests are running and queued right now, and open tunnels with their status.
- 03Test Manager projects, folders, test cases, and test runs with passed, failed and skipped totals.
- 04When asked and granted, marks a session passed or failed, renames it, stops or deletes it, and renames, stops or deletes a build. The dashboard and reports show the change.
- 05When asked and granted, stops a running tunnel, so tests that need it fail until it is restarted.
- 06When asked and granted, creates Test Manager projects, test cases and runs, sets a test's result or assignee, and archives or deletes runs and test cases.
Acts when asked
When you ask it to
These tools change something in LambdaTest. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
- 01Mark a test session passed or failed, rename or retag it
- 02Stop a running test session
- 03Delete a test session
- 04Rename a build
- 05Stop every running test in a build
- 06Delete a build
- 07Stop a running tunnel
- 08Create a Test Manager project
- 09Create test cases in a Test Manager folder
- 10Create a test run
- 11Set a test run instance's result or assignee
- 12Archive a test run
- 13Delete a test run
- 14Delete a test case
In practice
Ask it like you would a colleague
Once LambdaTest is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
LambdaTest + MemtroWhich sessions failed in the nightly build?
How many tests are running and queued right now?
Which tunnels are open?
How far has the release regression test run got?
Mark session 8812 as failed with the reason checkout timeout.
Result recorded
Dan Fletcher, test engineer at Northwind, asked Memtro to record a failed result for a checkout test in the release run. With the action granted, Memtro set it to Failed in Test Manager. The run totals changed for everyone following the release.
Teams
Where it fits
The teams that lean on LambdaTest most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in LambdaTest is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
- Work managementLambdaTest with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementLambdaTest with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementLambdaTest with LinearIssues, projects and teams, synced hourly into memory.
- SupportLambdaTest with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportLambdaTest with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportLambdaTest with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisLambdaTest with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisLambdaTest with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisLambdaTest with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- BugSnag
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withUsername and access key
- 1
In LambdaTest, open the profile menu → Account Settings → Password & Security and copy your username and access key. The key has your access.
- 2
In Memtro, open Connections → LambdaTest and paste the Username and the Access key. Set the Region to eu if your account is on the EU data centre.
- 3
An administrator grants the actions by name, such as Stop a running test session, to the teams that may use them.
- 4
Ask "Which sessions failed in the nightly build?"
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The LambdaTest tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in LambdaTest?+
Only when you ask, and only what it has been granted: mark a test session passed or failed, rename or retag it; stop a running test session; delete a test session; rename a build; stop every running test in a build; delete a build; stop a running tunnel; create a Test Manager project; create test cases in a Test Manager folder; create a test run; set a test run instance's result or assignee; archive a test run; delete a test run; delete a test case. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
Who can use a LambdaTest connection?+
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my LambdaTest data?+
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
How do I connect LambdaTest?+
Username and access key. In LambdaTest, open the profile menu → Account Settings → Password & Security and copy your username and access key. The key has your access.
Connect LambdaTest in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.