DEVOPS

Weekly Flaky-Test Digest with Notion Leaderboard

Every week this workflow rolls up which tests were quarantined, who owns them, and how long they've been skipped.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery active and closed quarantines from PostgresPostgreSQLPostgres
  • LogicRank by skip age and flag overdue items
  • ActionPublish leaderboard to NotionNotionNotion
  • OutputPost top offenders to Microsoft TeamsMicrosoft Teams

What it does

Gives engineering leadership a recurring, readable picture of quarantine health: how many tests are skipped right now, which are overdue past their one-cycle promise, and which owners have the most outstanding flakes. It turns scattered quarantine tickets into a single accountable scoreboard.

When to use it

Use it when quarantine is in place but nobody can see the aggregate debt. Ideal for a weekly engineering review where you want to spotlight overdue skips and the teams responsible.

How it works

  1. 1A weekly schedule triggers the digest.
  2. 2The workflow queries the quarantine tracking database in Postgres for all active and recently closed skips.
  3. 3A logic step ranks tests by skip age and groups outstanding items by owner, flagging anything past one cycle.
  4. 4It writes the ranked leaderboard to a Notion page for the engineering review.
  5. 5It posts the top overdue offenders and totals to Microsoft Teams as the final delivery.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.