Labsco
MCP SERVER

MicroShift Test Analyzer

by kasturinarra

Ask which MicroShift versions the test failures cluster around, straight from the results sheet.

Automated Testing & QA
Summary
Test failures read by version, not by run.

The question a release raises is whether a failure is new, and this cuts the results sheet along that line — by version, by pipeline over time, by failure reason — so the comparison takes one question instead of an afternoon of filtering.

What it is

A Python MCP server over a Google Sheet of MicroShift test results. It groups failed pipelines by MicroShift version, aggregates failures across versions, tracks one pipeline over time, searches failure reasons, and compares two versions.

What you get
  • Failed testing pipelines grouped by MicroShift version
  • Aggregate failure statistics across all versions
  • Failure trends for a named pipeline over time
  • A search across the recorded failure reasons
  • Two MicroShift versions compared against each other
  • Data read from the sheet on each request rather than from a cached copy
Requirements

A Google Cloud service account with the Sheets API enabled, its client email and private key in .env, and the spreadsheet shared with that service-account address as a viewer. The spreadsheet id is a constant near the top of server.py — edit it there to point at your own sheet.