Skip to content

Main content

Random Paginated API Response Sequence Generator

Partition shuffled supplied records into synthetic cursor pages, optional empty pages, and parser-checked next links with consistent termination.

Loading tool…

Description

Partition shuffled supplied records into synthetic cursor pages, optional empty pages, and parser-checked next links with consistent termination.

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.

Partition shuffled supplied records into synthetic cursor pages, optional empty pages, and parser-checked next links with consistent termination.

When to use this tool

Use this generator to create reproducible paginated api response sequence 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 records, minimumPageSize, maximumPageSize, emptyPageProbability, terminalEmptyPage 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 pages, recordOrder. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Shuffle unique records and partition them with sampled page sizes, optionally inserting empty intermediate pages and a terminal empty page. Assign explicit cursors, build next Link headers, and delegate their parsing.1

Delegated operations used for this result: query string; link header parser. Their calculation or parsing conventions apply to the corresponding result fields.2, 3

Input fieldMeaning and unitsAccepted input
recordsRecordsRequired. Array of Object; no unknown keys.; minimum items 0; maximum items 128.
records[].idLiteral identifier used to match records, independently of their display labels.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
records[].valueValueRequired. Text; maximum UTF-16 length 4096.
minimumPageSizeMinimum Page SizeRequired. Safe integer; minimum 1; maximum 128.
maximumPageSizeMaximum Page SizeRequired. Safe integer; minimum 1; maximum 128.
emptyPageProbabilityEmpty Page ProbabilityRequired. Finite number; minimum 0; maximum 1.
terminalEmptyPageTerminal Empty PageRequired. Boolean.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
pagesPagesRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 128.
pages[].cursorCursorRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
pages[].recordsRecordsRequired. Array of Object; no unknown keys.; minimum items 0; maximum items 128.
pages[].records[].idLiteral identifier used to match records, independently of their display labels.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
pages[].records[].valueValueRequired. Text; maximum UTF-16 length 4096.
pages[].nextCursorNext CursorRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 128. or Null.
pages[].linkHeaderLink HeaderRequired. Text; maximum UTF-16 length 4096.
pages[].parsedLinkTargetsParsed Link TargetsRequired. Array of Text; maximum UTF-16 length 4096.; minimum items 0; maximum items 1.
recordOrderRecord OrderRequired. Array of Text; minimum UTF-16 length 1; maximum UTF-16 length 128.; minimum items 0; maximum items 128.
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": {
    "records": [
      {
        "id": "a",
        "value": "alpha"
      },
      {
        "id": "b",
        "value": "beta"
      },
      {
        "id": "c",
        "value": "gamma"
      }
    ],
    "minimumPageSize": 1,
    "maximumPageSize": 2,
    "emptyPageProbability": 0.5,
    "terminalEmptyPage": true,
    "seed": 42
  },
  "output": {
    "pages": [
      {
        "cursor": "page-1",
        "records": [
          {
            "id": "c",
            "value": "gamma"
          },
          {
            "id": "a",
            "value": "alpha"
          }
        ],
        "nextCursor": "page-2",
        "linkHeader": "</items?cursor=page-2&limit=2>; rel=\"next\"",
        "parsedLinkTargets": [
          "/items?cursor=page-2&limit=2"
        ]
      },
      {
        "cursor": "page-2",
        "records": [
          {
            "id": "b",
            "value": "beta"
          }
        ],
        "nextCursor": "page-3",
        "linkHeader": "</items?cursor=page-3&limit=2>; rel=\"next\"",
        "parsedLinkTargets": [
          "/items?cursor=page-3&limit=2"
        ]
      },
      {
        "cursor": "page-3",
        "records": [],
        "nextCursor": null,
        "linkHeader": "",
        "parsedLinkTargets": []
      }
    ],
    "recordOrder": [
      "c",
      "a",
      "b"
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • An empty page can still have a nextCursor; consumers must not infer termination from record count alone. All original records appear once and no endpoint is contacted.
  • 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 Paginated API Response Sequence Generator — tool.io

  2. Calculation or validation: format/query-string — tool.io

  3. Calculation or validation: http/link-header-parser — tool.io

Similar or alternative tools

  • Random SSE Event Sequence Fixture Generator

    Serialize supplied multiline SSE frames with explicit newline and final-dispatch controls and delegate event, ID and retry parsing.

  • 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.