Description
Construct supported Boolean-attribute spellings with lexical parser outputs, separate presence-based interpretation and author-spelling keys, including the nonconforming false-value control.
A protocol fixture is local test data representing headers, messages, identifiers, or request decisions. Serialization and parsing can be checked without contacting a server, while authentication, delivery, and actual client behavior require separate tests.
Construct supported Boolean-attribute spellings with lexical parser outputs, separate presence-based interpretation and author-spelling keys, including the nonconforming false-value control.
When to use this tool
Use this generator to create reproducible html boolean attribute 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 attributes, variants, 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.
Draw a supported Boolean attribute and absent, bare, empty, name-valued, or false-valued spelling on its matching element. Parse presence and report interpreted true whenever the attribute exists, with false spelling marked nonconforming.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| attributes | Attributes | Required. Array of Text; one of "disabled", "checked", "required", "multiple", "readonly", "autofocus", "open".; minimum items 1; maximum items 7. |
| variants | Variants | Required. Array of Text; one of "absent", "bare", "empty", "name", "false".; 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[].attribute | Attribute | Required. Text; one of "disabled", "checked", "required", "multiple", "readonly", "autofocus", "open". |
| cases[].variant | Variant | Required. Text; one of "absent", "bare", "empty", "name", "false". |
| cases[].tag | Tag | Required. Text; maximum UTF-16 length 131072. |
| cases[].parsed | Parsed | Required. Object; no unknown keys. |
| cases[].parsed.name | Name | Required. Text; maximum UTF-16 length 256. |
| cases[].parsed.attributes | Attributes | Required. Array of Object; no unknown keys.; minimum items 0; maximum items 16. |
| cases[].parsed.attributes[].name | Name | Required. Text; maximum UTF-16 length 256. |
| cases[].parsed.attributes[].value | Value | Required. Text; maximum UTF-16 length 2048. |
| cases[].present | Present | Required. Boolean. |
| cases[].interpreted | Interpreted | Required. Boolean. |
| cases[].spellingConforming | Spelling Conforming | Required. Boolean. |
| 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": {
"attributes": [
"disabled"
],
"variants": [
"absent",
"bare",
"empty",
"name",
"false"
],
"count": 2,
"seed": 42
},
"output": {
"cases": [
{
"attribute": "disabled",
"variant": "empty",
"tag": "<button disabled=\"\">",
"parsed": {
"name": "button",
"attributes": [
{
"name": "disabled",
"value": ""
}
]
},
"present": true,
"interpreted": true,
"spellingConforming": true
},
{
"attribute": "disabled",
"variant": "name",
"tag": "<button disabled=\"disabled\">",
"parsed": {
"name": "button",
"attributes": [
{
"name": "disabled",
"value": "disabled"
}
]
},
"present": true,
"interpreted": true,
"spellingConforming": true
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- An HTML Boolean attribute spelled false still means present. This fixture does not evaluate live DOM properties, scripting, interaction, or full element conformance.
- 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 HTML Attribute Quoting Corpus Generator
Compose bounded benign start-tag source with caller text, delegated five-character entity escaping, feasible double/single/unquoted/Boolean attribute forms, and duplicate attributes; retain the lexical parser's raw character references and first-duplicate rule, not DOM-decoded values, sanitization, or HTML conformance certification.
- Random HTML Text Extraction Corpus Generator
Compose bounded escaped paragraph/span/emphasis, comment, inert-script, and comment-only-style source from supplied text, then delegate text extraction, tag stripping, and comment removal separately; retain raw source and entity conventions without executing markup/scripts, browser layout equivalence, or sanitization claims.