Skip to content
Notis

Retrospective Findings Become Regression Tests Automatically

Document a retrospective finding, a regression test is created. Problems don't happen twice.

Trigger

Comment Received Trigger

Triggered when a comment is received.

Action

Create Multi Test

Tool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."

Why this helps

Retrospective findings identify recurring issues but these insights rarely translate into preventative tests, causing the same problems to repeat in future releases.

  • Prevent identified issues from recurring in future releases
  • Turn retrospective insights into executable prevention
  • Maintain growing regression coverage based on real incident history

Setup

Build it in a few focused steps.

  • 1Connect Linear and Blazemeter to Notis.
  • 2Create an automation: 'When a Linear issue comment documents retrospective findings, create a regression test suite in Blazemeter that validates those issues won't recur, testing the specific scenarios mentioned.'
  • 3Select 'Comment Received' as your trigger.
  • 4Choose your notification channel.
  • 5Test by commenting on a Linear issue with 'retrospective finding: latency spikes when cache is disabled' and verify a regression test is created in Blazemeter within one minute.

Questions about this workflow

What if retrospective findings are vague or non-technical?

Provide specific technical details in your comment, e.g., 'regression test: verify latency stays <300ms when connections spike.' Vague findings create imprecise tests.

Should regression tests run once or continuously?

Specify in your prompt: 'add to continuous regression suite' to make it permanent, or 'create as one-time test' if it's a one-off scenario.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Linear to Blazemeter. A trigger fires from one place; an action lands in another.

Linear triggers

Blazemeter actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create API Monitoring Schedule

Tool to create a new schedule for running api monitoring tests. use when you need to automate test runs at defined intervals after determining the correct cron expression and test or collection id.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Multi Test

Tool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."

ActionInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Create Project

Tool to create a new project. use when you need to initialize a project in a specific workspace. use after confirming the workspace id.

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Create Test

Tool to create a new single test within a specified project. use when registering a new performance test via api.

ActionInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

TriggerInstant

Delete API Monitoring Schedule

Tool to delete a specific test schedule by its id. use when you need to remove a scheduled test by its unique schedule identifier.

ActionInstant

Private Team Comment Created

Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).

TriggerPolling

Get Accounts

Tool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.

ActionInstant

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Get API Monitoring Schedule

Tool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.

ActionInstant

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

TriggerPolling

Get API Monitoring Schedules

Tool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.

ActionInstant

Connect any two apps with Notis in the middle.

Linear and Blazemeter, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Blazemeter.