Description
Generate badge combinations only from supplied allowed label/severity/counter rules, retaining full labels and bounded optional counters.
An interface fixture makes content and state explicit so a consumer can test a rendering or interaction. Literal labels, modeled states, and calculated geometry remain separate from what a browser or assistive technology actually displays or announces.
Generate badge combinations only from supplied allowed label/severity/counter rules, retaining full labels and bounded optional counters.
When to use this tool
Use this generator to create reproducible badge status combination fixture cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.
How to use the tool and how it works
- Supply rules, maximumCounter, count in the field shapes below. Set seed when you need an explicit replay.
- Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
- Read badges. Use the conventions below. Keep answer-bearing fields separate when presenting an exercise.
Sample badge rules preserving their supplied label and severity, make a 24-code-point preview, and draw an inclusive integer counter only when that rule permits one. Otherwise return null counter.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| rules | Rules | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| rules[].label | Supplied display label. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| rules[].severity | Severity | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| rules[].counterAllowed | Counter Allowed | Required. Boolean. |
| maximumCounter | Maximum Counter | Required. Safe integer; minimum 0; maximum 9007199254740991. |
| count | Count | Required. Safe integer; minimum 1; maximum 32. |
| seed | Optional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed. | Optional. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| badges | Badges | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| badges[].label | Supplied display label. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| badges[].preview | Preview | Required. Text; maximum UTF-16 length 256. |
| badges[].severity | Severity | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| badges[].counter | Counter | Required. Safe integer; minimum 0; maximum 9007199254740991. or Null. |
| randomness | Replay source and normalized 32-bit seed, or null seed for an advancing context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional safe-integer replay seed; normalization and precedence are explained below. | Required. Safe integer. or Null. |
| randomness.source | Source | Required. Text; one of "context", "seed". |
An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.
{
"input": {
"rules": [
{
"label": "Ready",
"severity": "success",
"counterAllowed": false
},
{
"label": "Pending",
"severity": "warning",
"counterAllowed": true
}
],
"maximumCounter": 4,
"count": 2,
"seed": 42
},
"output": {
"badges": [
{
"label": "Pending",
"preview": "Pending",
"severity": "warning",
"counter": 2
},
{
"label": "Pending",
"preview": "Pending",
"severity": "warning",
"counter": 3
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Zero is a present counter and differs from null. Severity is supplied metadata rather than inferred urgency, and the fixture does not render badges, measure layout, or implement notifications.
- A replay requires the same complete input and implementation. The stated sampling convention applies within its eligible space. A finite draw does not exhaust all possible outputs; repeats remain possible unless a distinct-selection rule is explicit.
- The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.
Alternative or Complementary methods
For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.
References
Similar or alternative tools
- Random Accordion Content Fixture Generator
Sample supplied accordion section content with independent expansion flags and codepoint previews; these synthetic fixtures do not execute a browser.
- Random ARIA State Transition Fixture Generator
Generate role/state snapshots and attempted transitions under caller-reviewed consistency edges, checking state tokens lexically without certifying role applicability or accessibility.