Random Modal Stack State Fixture Generator

Description

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.

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 dialog open, top-close and labeled orphan-close attempts with parent ownership and stack snapshots under a synthetic policy; focus behavior requires app tests.

When to use this tool

Use this generator to create reproducible modal stack 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 dialogs, eventCount 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 events, finalStack. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Sample open, close, and orphan-close events. Opening records a new modal whose parent is the current top; closing succeeds only for a nonempty stack and orphan-close is rejected. Return stack IDs after every event.^[1]

Input field	Meaning and units	Accepted input
dialogs	Dialogs	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 1; maximum items 32.
eventCount	Event 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
events	Events	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
events[].action	Action	Required. Text; one of "open", "close", "orphan-close".
events[].targetId	Target Id	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 32.
events[].title	Title	Required. Text; maximum UTF-16 length 256.
events[].parentId	Parent Id	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 32. or Null.
events[].accepted	Accepted	Required. Boolean.
events[].stack	Stack	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 32.; minimum items 0; maximum items 32.
finalStack	Final Stack	Required. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 32.; minimum items 0; 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.

json

{
  "input": {
    "dialogs": [
      "Settings",
      "Help"
    ],
    "eventCount": 2,
    "seed": 42
  },
  "output": {
    "events": [
      {
        "action": "open",
        "targetId": "modal-0",
        "title": "Settings",
        "parentId": null,
        "accepted": true,
        "stack": [
          "modal-0"
        ]
      },
      {
        "action": "orphan-close",
        "targetId": "absent",
        "title": "",
        "parentId": null,
        "accepted": false,
        "stack": [
          "modal-0"
        ]
      }
    ],
    "finalStack": [
      "modal-0"
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

Rejected closes are modeled events rather than execution failures. Parent IDs describe the opening-time stack; focus trapping, restoration, rendering, and accessibility behavior are not simulated.
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

Tool behavior and example: Random Modal Stack State Fixture Generator — tool.io

Similar or alternative tools

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.
Random Rating Widget State Fixture Generator
Draw bounded integer rating ticks under a supplied maximum and subdivision contract, retaining fractional fills and disabled states with caller labels.