Repository navigation
v0.8.0
Kinora 0.8.0
This release tells flaky tests from broken ones, even when your suite runs without retries.
Flaky and broken tests
- The Tests and Components pages now flag each test or story as Flaky or Broken over its last 20 runs, instead of a single "Unstable" count. Hover the badge to see why.
- A test is flaky when it passed and failed on the same commit, needed a retry to pass, or keeps flipping between pass and fail. Flakiness now shows up for Vitest and Storybook suites, which run without retries by default.
- A test is broken when it fails and keeps failing. Its page links to the run where it started failing, with the commit.
- Filter each list on Needs attention, Flaky or Broken. Links shared with the previous
?unstable=filter still open the same list. - See Flaky and broken tests for the exact rules.
MCP
@kinora/mcp0.3.0:test_historyandcomponent_healthreturn thehealthof each test or story (stable,flakyorbroken) with its reason, andcomponent_healthcan filter on it.