Description
Construct bounded synthetic toast arrivals with lifetime, priority, dismissal and explicit duplicate-ID controls; notification rendering remains app-owned.
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 bounded synthetic toast arrivals with lifetime, priority, dismissal and explicit duplicate-ID controls; notification rendering remains app-owned.
When to use this tool
Use this generator to create reproducible toast notification burst 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 messages, eventCount, maximumGap, duration, duplicateProbability 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. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.
Arrival times accumulate inclusive integer gaps from zero. Each toast draws a message and priority; duplicate IDs reuse the immediately preceding toast ID according to duplicateProbability. Expiry is arrival plus duration, while independently selected dismissals occur within that duration.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| messages | Messages | 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. |
| maximumGap | Maximum Gap | Required. Safe integer; minimum 0; maximum 9007199254740991. |
| duration | Duration | Required. Safe integer; minimum 1; maximum 9007199254740991. |
| duplicateProbability | Duplicate Probability | Required. Finite number; minimum 0; maximum 1. |
| 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[].id | Literal identifier used to match records, independently of their display labels. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 32. |
| events[].message | Message | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. |
| events[].preview | Preview | Required. Text; maximum UTF-16 length 256. |
| events[].arrival | Arrival | Required. Safe integer; minimum 0; maximum 9007199254740991. |
| events[].expires | Expires | Required. Safe integer; minimum 0; maximum 9007199254740991. |
| events[].priority | Priority | Required. Text; one of "normal", "urgent". |
| events[].dismissedAt | Dismissed At | Required. Safe integer; minimum 0; maximum 9007199254740991. or Null. |
| events[].duplicate | Duplicate | 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": {
"messages": [
"Saved",
"Queued"
],
"eventCount": 2,
"maximumGap": 0,
"duration": 4,
"duplicateProbability": 1,
"seed": 42
},
"output": {
"events": [
{
"id": "toast-0",
"message": "Saved",
"preview": "Saved",
"arrival": 0,
"expires": 4,
"priority": "urgent",
"dismissedAt": 2,
"duplicate": false
},
{
"id": "toast-0",
"message": "Queued",
"preview": "Queued",
"arrival": 0,
"expires": 4,
"priority": "urgent",
"dismissedAt": 4,
"duplicate": true
}
],
"randomness": {
"seed": 42,
"source": "seed"
}
}
}Limitations and assumptions
- Times are synthetic milliseconds. Duplicate IDs deliberately exercise consumer handling; neither notification delivery nor interface behavior is executed. Combined times must remain safe integers.
- 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 Notification Inbox Dataset Generator
Compose supplied notification templates into a synthetic inbox with feasible read timestamps, chronological order, and unread and category counts.
- 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.