Eval suite bars
Pass rate per eval suite, against its own target.
Definition · Updated Nov 2, 2026
Eval suite bars show each test suite's pass rate as a bar with its passed and total counts, against that suite's own target tick. Suites below target take their own colour. Use it to review a model or prompt across its eval suites before shipping.
Pay once. Every update included.
Live preview
Sample data: six eval suites, refunds-v4 95.8% (46 / 48), invoices-v9 100% (120 / 120)
- Data shape
- Passed and total per suite, a target
- Good for
- Eval suites, test runs, QA checks
- Avoid when
- There is no target
- Sizes
- XS, S, M and L, re-laid out from the data
Anatomy
Inspect it like the Figma file.
The same layers, names and tokens as the component. Select one to read its size, fill and style.
Layers
102 / Eval suite bars
- Layer
- pass · refunds-v4
- Type
- Rectangle
- Size
- 429 × 6
- Fill
- status/danger
- Radius
- 3
- Group
- Marks · 12
Layers
102 / Eval suite bars
- Layer
- pass · refunds-v4
- Type
- Rectangle
- Size
- 176 × 6
- Fill
- status/danger
- Radius
- 3
- Group
- Marks · 12
Layers
102 / Eval suite bars
- Layer
- pass · refunds-v4
- Type
- Rectangle
- Size
- 99 × 6
- Fill
- status/danger
- Radius
- 3
- Group
- Marks · 12
Sizes
Re-laid out, never scaled.
The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.
M against S
Width360 px480 px
Plot328 px440 px
Labels1521
Marks1212
Height212 px246 px
Same tokens at every size: text styles, 1 px lines and mark radius stay put.
When to use
Ready to ship?
Three signs it fits, and three signs another type fits better.
Is there a target pass rate?
Just pass rates to rank.
Yes: Keep the eval suite bars
Is it one model?
Many models against many suites.
Yes: Keep the eval suite bars
Code and Figma
One name in Figma and in code.
Every Figma property is a prop with the same name and values. One command installs it.
Figma
chart/102-eval-suite-bars
npx shadcn add @chartory/eval-suite-barsimport { EvalSuiteBars } from "@/components/chartory/eval-suite-bars"import { suiteResults } from "./suite-results"export function SuiteResults() { return ( <EvalSuiteBars data={suiteResults} size="m" legend={true} /> )}Hearth widget
Eval suite bars as a widget.
The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.
EmberPreset
ChartoryDefault preset
Pick the blocks, the size and the preset for your own widget.
Read the Hearth widget docsFAQ
Eval suite bars questions.
What people ask before they put eval suite bars in a dashboard.
Something else?
hello@usechartory.comA rate on 48 cases and a rate on 180 cases are not equally sure. Each bar shows both (46 / 48, 95.8%) so a small suite is read with care.
Pass rates sit close together near the top, so the axis covers 80% to 100% to make the gaps between suites visible.
One data object in the sample’s shape: passed and total per suite, a target. The docs page lists every field and links its JSON Schema; the sample data comes with the component, so you can start from it and swap in your own.
Series take the preset’s data colours in order, and states such as up, down or warning take its status colours. Change the preset in Figma or in code to recolour every chart at once.
XS, S, M and L, in light and dark. Each size is laid out again from the data, so text and lines keep their size.
Yes. It plays in when it scrolls into view, and when the data changes every mark moves from its old place to its new one. With reduced motion on, it does not move.
Yes. The Figma component comes with Figma and Complete, the React component with Code and Complete.
Ask for it by name. The MCP server tells the agent what data it needs and runs the same command: npx shadcn add @chartory/eval-suite-bars. You review the diff.
Related types
Other ways to show compare items.
The same question, a different shape of answer. Every type ships in Figma and in code.
Same family
Compare items
Rank, gap and change between products, teams or regions.