Description
Draw bounded integer rating ticks under a supplied maximum and subdivision contract, retaining fractional fills and disabled states with caller labels.
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.
Draw bounded integer rating ticks under a supplied maximum and subdivision contract, retaining fractional fills and disabled states with caller labels.
When to use this tool
Use this generator to create reproducible rating widget state 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 labels, maximum, subdivisions, 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 states. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Draw an integer rating tick from zero through maximum times subdivisions and divide by subdivisions. Return whole and fractional portions, independently drawn disabled state, a label preview, and each item's clamped fill fraction.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| labels | Labels | Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 1; maximum items 32. |
| maximum | Maximum | Required. Safe integer; minimum 1; maximum 32. |
| subdivisions | Subdivisions | Required. Safe integer; minimum 1; maximum 32. |
| count | Requested count; the mechanics explain whether one draw expands into several returned records. | 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 |
|---|---|---|
| states | States | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| states[].label | Caller-facing text label; not a globally unique identifier. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| states[].value | Value | Required. Finite number; minimum 0; maximum 32. |
| states[].whole | Whole | Required. Safe integer; minimum 0; maximum 32. |
| states[].fraction | Fraction | Required. Finite number; minimum 0; strictly below 1. |
| states[].disabled | Disabled | Required. Boolean. |
| states[].fills | Fills | Required. Array of Finite number; minimum 0; maximum 1.; minimum items 1; maximum items 32. |
| randomness | Replay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source. | Required. Object; no unknown keys. |
| randomness.seed | Optional numeric 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": {
"labels": [
"Quality",
"Comfort"
],
"maximum": 3,
"subdivisions": 2,
"count": 1,
"seed": 42
},
"output": {
"states": [
{
"label": "Comfort",
"value": 2,
"whole": 2,
"fraction": 0,
"disabled": true,
"fills": [
1,
1,
0
]
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
} Limitations and assumptions
- The grid includes both zero and the maximum. This is state data, not rendered stars, pointer behavior, keyboard semantics, or an accessibility audit; labels are previewed by code point.
- A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
- 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 Modal Stack State Fixture Generator
Construct dialog open, top-close and labeled orphan-close attempts with parent ownership and stack snapshots under a synthetic policy; focus behavior requires app tests.
- Random Pagination Control State Fixture Generator
Generate legal pagination control states and disabled-button/item-range expectations, using page zero for empty collections and no API record bodies.