Checking release readiness
Dan Fletcher, QA lead at Northwind, asked whether the release runs were clean. Memtro listed the week's runs with their status, the failed results, and the open defects found in them.
Qase + Memtro
Which test runs failed this week, and which defects are still open?
Qase shows you projects with case, run and defect counts, and test cases by suite, milestone, severity, priority or status. It reads test runs with pass and fail counts, results, defects, milestones and test plans. When asked and granted, it can create, edit or delete test cases, start, complete or delete runs, and record results. It can also file, edit, resolve or delete defects, and create milestones, suites and plans. Qase can tell Memtro as it happens when a run completes or a defect is filed, and a job can start on it. Those webhooks are set per project.
In Memtro
What you can do with Qase in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Qase tool, reads what it needs, and answers with the source cited.
What it does
- 01Lists projects with counts of cases, suites, milestones, active runs and open defects.
- 02Reads test cases by suite, milestone, severity, priority, status or automation.
- 03Reads runs with their status and times, individual results, defects, milestones and test plans.
- 04When asked and granted, creates, edits or deletes test cases, or creates milestones, suites and plans.
- 05When asked and granted, starts or completes a run, records a result, or files, resolves or deletes a defect, visible to the project team.
- 06With events on, a test run completed, a defect filed or a defect resolved in Qase can start a job.
Acts when asked
When you ask it to
These tools change something in Qase. 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.
- 01Create a test case
- 02Edit a test case
- 03Delete a test case
- 04Start a test run
- 05Complete a test run
- 06Delete a test run and its results
- 07Record a test result in a run
- 08File a defect
- 09Edit a defect
- 10Resolve a defect
- 11Set a defect to in progress, resolved or invalid
- 12Delete a defect
- 13Create a milestone
- 14Create a test suite
- 15Create a test plan
Events
When it happens
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Qase, choosing the same kinds; the tab shows Qase's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Qase sends a secret with every delivery, and one without it is refused.
Events and webhooks- 01A test run started
- 02A test run completed (passed or failed)
- 03A test run was aborted
- 04A test run was changed or had cases added or removed
- 05A test run was deleted
- 06A test result was recorded
- 07A test result was changed
- 08A defect was filed
- 09A defect was changed
- 10A defect was resolved
- 11A defect was deleted
- 12A test case was created
- 13A test case was changed
- 14A test case was deleted
- 15A test suite was created
- 16A test plan was created
- 17A milestone was created
- 18A milestone was changed
- 19A test case was submitted for review
- 20A test case review was merged
- 21A test case review was declined
In practice
Ask it like you would a colleague
Once Qase 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.
Qase + Memtro
Which runs failed this week?
Which defects are still open on the mobile project?
Which critical test cases are in the checkout suite?
Which cases are in the release test plan?
Which milestones are due this month?
A failed run triaged
When a test run completed in Qase, a job started for Priya Sharma at Acme Ltd. It read the run's failed results and the defects already filed, and listed which failures had no defect yet.
Teams
Where it fits
The teams that lean on Qase 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 Qase 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 managementQase with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementQase with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementQase with LinearIssues, projects and teams, synced hourly into memory.
- SupportQase with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportQase with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportQase with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisQase with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisQase with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisQase 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
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor
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 withAPI token
- 1
In Qase open your avatar, then API tokens, and create a token. It has your role's access, so a dedicated user with only the projects Memtro needs is safer.
- 2
In Memtro open Connections → Qase and paste the API token. Fill in Enterprise workspace address only if you sign in on your own domain.
- 3
An administrator grants the case, run and defect actions by name. Events are turned on from the connection's Events tab, and the address is then added in each project's webhook settings in Qase.
- 4
Ask: which runs failed this week?
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Qase tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in Qase?+
Only when you ask, and only what it has been granted: create a test case; edit a test case; delete a test case; start a test run; complete a test run; delete a test run and its results; record a test result in a run; file a defect; edit a defect; resolve a defect; set a defect to in progress, resolved or invalid; delete a defect; create a milestone; create a test suite; create a test plan. 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 Qase 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 Qase 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 Qase?+
API token. In Qase open your avatar, then API tokens, and create a token. It has your role's access, so a dedicated user with only the projects Memtro needs is safer.
Can Qase start a job?+
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Qase, choosing the same kinds; the tab shows Qase's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Connect Qase in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.