Skip to content

Main content

Random Stack Operation Trace Generator

Generate sampled push, pop and peek operations with bottom-to-top LIFO snapshots, explicit empty-stack underflows and a delegated top-first final view.

Loading tool…

Description

Generate sampled push, pop and peek operations with bottom-to-top LIFO snapshots, explicit empty-stack underflows and a delegated top-first final view.

An operation trace pairs an ordered request stream with the state after each step. Empty operations, ties, evictions, and boundary indexes are part of the modeled contract rather than incidental display details.

Generate sampled push, pop and peek operations with bottom-to-top LIFO snapshots, explicit empty-stack underflows and a delegated top-first final view.

When to use this tool

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

Sample push, pop, or peek operations. Push draws a supplied value; pop removes the last value and peek reads it. Return a bottom-to-top snapshot after each operation, explicit underflow flags and null values for empty reads, plus a delegated top-first final view.1

Delegated operations used for this result: reverse. Their calculation or parsing conventions apply to the corresponding result fields.2

Input fieldMeaning and unitsAccepted input
initialValuesInitial ValuesRequired. Array of Text; maximum UTF-16 length 64.; minimum items 0; maximum items 16.
valuesValuesRequired. Array of Text; maximum UTF-16 length 64.; minimum items 1; maximum items 16.
operationsOperationsRequired. Array of Text; one of "push", "pop", "peek".; minimum items 1; maximum items 3.
eventCountEvent CountRequired. Safe integer; minimum 1; maximum 64.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
eventsEventsRequired. Array of Object; no unknown keys.; minimum items 0; maximum items 64.
events[].kindKindRequired. Text; one of "push", "pop", "peek".
events[].valueValueRequired. Text; maximum UTF-16 length 64. or Null.
events[].underflowUnderflowRequired. Boolean.
events[].stackStackRequired. Array of Text; maximum UTF-16 length 64.; minimum items 0; maximum items 80.
finalStackFinal StackRequired. Array of Text; maximum UTF-16 length 64.; minimum items 0; maximum items 80.
finalTopFirstFinal Top FirstRequired. Array of Text; maximum UTF-16 length 64.; minimum items 0; maximum items 80.
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": {
    "initialValues": [
      "a"
    ],
    "values": [
      "b",
      "c"
    ],
    "operations": [
      "pop",
      "push",
      "peek"
    ],
    "eventCount": 4,
    "seed": 42
  },
  "output": {
    "events": [
      {
        "kind": "push",
        "value": "b",
        "underflow": false,
        "stack": [
          "a",
          "b"
        ]
      },
      {
        "kind": "peek",
        "value": "b",
        "underflow": false,
        "stack": [
          "a",
          "b"
        ]
      },
      {
        "kind": "peek",
        "value": "b",
        "underflow": false,
        "stack": [
          "a",
          "b"
        ]
      },
      {
        "kind": "pop",
        "value": "b",
        "underflow": false,
        "stack": [
          "a"
        ]
      }
    ],
    "finalStack": [
      "a"
    ],
    "finalTopFirst": [
      "a"
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • Underflow is an intentional trace event rather than an invalid outer input. Snapshot work is bounded. Duplicate values are allowed and this does not execute a concurrent stack implementation.
  • 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 Stack Operation Trace Generator — tool.io

  2. Calculation or validation: list/reverse — tool.io

Similar or alternative tools