Description
Construct supported progress/meter attribute boundaries and labeled reversed/indeterminate controls, retaining actual core values or expected normalized-bound errors without real process monitoring.
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.
Construct supported progress/meter attribute boundaries and labeled reversed/indeterminate controls, retaining actual core values or expected normalized-bound errors without real process monitoring.
When to use this tool
Use this generator to create reproducible progress meter boundary 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 progress, meter, modes, 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 cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Copy the supplied progress and meter models and apply the selected below, above, reversed, indeterminate, or baseline mode. Delegate progress percentage and meter-band interpretation, retaining expected reversed-bound meter errors separately from successful results.1
Delegated operations used for this result: progress value max percent; meter optimum low high band classifier. Their calculation or parsing conventions apply to the corresponding result fields.2, 3
| Input field | Meaning and units | Accepted input |
|---|---|---|
| progress | Progress | Required. Object; no unknown keys. |
| progress.hasValue | Has Value | Required. Boolean. |
| progress.value | Value | Required. Finite number. |
| progress.max | Max | Required. Finite number. |
| meter | Meter | Required. Object; no unknown keys. |
| meter.value | Value | Required. Finite number. |
| meter.min | Min | Required. Finite number. |
| meter.low | Low | Required. Finite number. |
| meter.high | High | Required. Finite number. |
| meter.max | Max | Required. Finite number. |
| meter.optimum | Optimum | Required. Finite number. |
| modes | Modes | Required. Array of Text; one of "valid", "below", "above", "reversed", "indeterminate".; minimum items 1; maximum items 5. |
| 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 |
|---|---|---|
| cases | Cases | Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32. |
| cases[].mode | Mode | Required. Text; one of "valid", "below", "above", "reversed", "indeterminate". |
| cases[].progress | Progress | Required. Object; no unknown keys. |
| cases[].progress.hasValue | Has Value | Required. Boolean. |
| cases[].progress.value | Value | Required. Finite number. |
| cases[].progress.max | Max | Required. Finite number. |
| cases[].meter | Meter | Required. Object; no unknown keys. |
| cases[].meter.value | Value | Required. Finite number. |
| cases[].meter.min | Min | Required. Finite number. |
| cases[].meter.low | Low | Required. Finite number. |
| cases[].meter.high | High | Required. Finite number. |
| cases[].meter.max | Max | Required. Finite number. |
| cases[].meter.optimum | Optimum | Required. Finite number. |
| cases[].progressResult | Progress Result | Required. Object; no unknown keys. |
| cases[].progressResult.indeterminate | Indeterminate | Required. Boolean. |
| cases[].progressResult.effectiveMax | Effective Max | Required. Finite number. |
| cases[].progressResult.effectiveValue | Effective Value | Required. Finite number. |
| cases[].progressResult.percent | Percent | Required. Finite number; minimum 0; maximum 100. |
| cases[].meterResult | Meter Result | Required. Object; no unknown keys. or Null. |
| cases[].meterError | Meter Error | Required. Object; no unknown keys. or Null. |
| cases[].html | Html | Required. Text; maximum UTF-16 length 131072. |
| 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": {
"progress": {
"hasValue": true,
"value": 3,
"max": 8
},
"meter": {
"value": 90,
"min": 0,
"low": 20,
"high": 80,
"max": 100,
"optimum": 10
},
"modes": [
"valid",
"below",
"above",
"reversed",
"indeterminate"
],
"count": 1,
"seed": 42
},
"output": {
"cases": [
{
"mode": "reversed",
"progress": {
"hasValue": true,
"value": 3,
"max": 8
},
"meter": {
"value": 90,
"min": 0,
"low": 100,
"high": 0,
"max": 100,
"optimum": 10
},
"progressResult": {
"indeterminate": false,
"effectiveMax": 8,
"effectiveValue": 3,
"percent": 37.5
},
"meterResult": null,
"meterError": {
"field": "low",
"code": "invalid_bounds"
},
"html": "<progress value=\"3\" max=\"8\"></progress><meter value=\"90\" min=\"0\" low=\"100\" high=\"0\" max=\"100\" optimum=\"10\"></meter>"
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Meter thresholds must initially satisfy min through low through high through max. Indeterminate progress is a hasValue state, not zero completion. These controls test calculation boundaries rather than browser rendering.
- 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 Heading Hierarchy Mutation Corpus Generator
Mutate caller heading sequences at a constructible interior position to introduce an upward skip, retaining baseline and mutated markup and the existing outline heuristic.
- Random Image Alt Context Fixture Generator
Pair caller image descriptions with decorative/informative contexts and missing-alt controls, retaining presence-check results without judging alternative-text quality.