Skip to content

Main content

Random Timeline Card Content Fixture Generator

Construct fictional event cards with elapsed integer ticks, optional supplied bodies and explicit reverse/swap chronology controls, reporting actual adjacent inversions.

Loading tool…

Description

Construct fictional event cards with elapsed integer ticks, optional supplied bodies and explicit reverse/swap chronology controls, reporting actual adjacent inversions.

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 fictional event cards with elapsed integer ticks, optional supplied bodies and explicit reverse/swap chronology controls, reporting actual adjacent inversions.

When to use this tool

Use this generator to create reproducible timeline card content 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

  1. Supply labels, bodies, count, minimumGap, maximumGap, order in the field shapes below. Set seed when you need an explicit replay.
  2. 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.
  3. Read cards, inversionIndices. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Each card adds an inclusive integer gap to its timestamp and samples a supplied label, sometimes adding body text. The chosen mode preserves order, reverses it, or swaps one adjacent pair. inversionIndices identifies the later position of each descending adjacent timestamp pair.1

Input fieldMeaning and unitsAccepted input
labelsLabelsRequired. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 1; maximum items 32.
bodiesBodiesRequired. Array of Text; maximum UTF-16 length 256.; minimum items 1; maximum items 32.
countRequested count; the mechanics explain whether one draw expands into several returned records.Required. Safe integer; minimum 1; maximum 32.
minimumGapMinimum GapRequired. Safe integer; minimum 0; maximum 9007199254740991.
maximumGapMaximum GapRequired. Safe integer; minimum 0; maximum 9007199254740991.
orderOrderRequired. Text; one of "ascending", "reverse", "swap".
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
cardsCardsRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
cards[].idLiteral identifier used to match records, independently of their display labels.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 32.
cards[].tickTickRequired. Safe integer; minimum 0; maximum 9007199254740991.
cards[].labelCaller-facing text label; not a globally unique identifier.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
cards[].previewPreviewRequired. Text; maximum UTF-16 length 256.
cards[].bodyBodyRequired. Text; maximum UTF-16 length 256. or Null.
inversionIndicesInversion IndicesRequired. Array of Safe integer; minimum 1; maximum 31.; minimum items 0; maximum items 31.
randomnessReplay 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.seedOptional numeric replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. 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": {
    "labels": [
      "Alpha",
      "Beta"
    ],
    "bodies": [
      "Body"
    ],
    "count": 3,
    "minimumGap": 2,
    "maximumGap": 2,
    "order": "reverse",
    "seed": 42
  },
  "output": {
    "cards": [
      {
        "id": "card-2",
        "tick": 6,
        "label": "Alpha",
        "preview": "Alpha",
        "body": null
      },
      {
        "id": "card-1",
        "tick": 4,
        "label": "Beta",
        "preview": "Beta",
        "body": null
      },
      {
        "id": "card-0",
        "tick": 2,
        "label": "Beta",
        "preview": "Beta",
        "body": null
      }
    ],
    "inversionIndices": [
      1,
      2
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Equal timestamps are not inversions. A swap can leave tied timestamps unchanged, so a mutation does not guarantee a detected inversion. Label previews count Unicode code points.
  • 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

  1. Tool behavior and example: Random Timeline Card Content Fixture Generator — tool.io

Similar or alternative tools