Skip to content

Main content

Random Web Manifest Mutation Corpus Generator

Mutate supplied manifest start URL, display, theme and icon fields and retain delegated parser outcomes plus member-shape labels.

Loading tool…

Description

Mutate supplied manifest start URL, display, theme and icon fields and retain delegated parser outcomes plus member-shape labels.

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.

Mutate supplied manifest start URL, display, theme and icon fields and retain delegated parser outcomes plus member-shape labels.

When to use this tool

Use this generator to create reproducible web manifest mutation corpus 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 template, mutations, count 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 cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Copy supplied manifest fields, draw one listed mutation per case and alter start URL, display, icons or theme shape accordingly. Serialize the object and retain delegated start-URL extraction/display results alongside icon-presence and theme-type checks.1

Delegated operations used for this result: manifest start url extractor; manifest display validator. Their calculation or parsing conventions apply to the corresponding result fields.2, 3

Input fieldMeaning and unitsAccepted input
templateTemplateRequired. Object; no unknown keys.
template.startUrlStart UrlRequired. Text; maximum UTF-16 length 65536.
template.displayDisplayRequired. Text; maximum UTF-16 length 65536.
template.themeColorTheme ColorRequired. Text; maximum UTF-16 length 65536.
template.iconSourcesIcon SourcesRequired. Array of Text; maximum UTF-16 length 65536.; minimum items 0; maximum items 8.
mutationsMutationsRequired. Array of Text; one of "remove-start", "wrong-start", "invalid-display", "remove-icons", "theme-null".; minimum items 1; maximum items 5.
countRequested count; the mechanics explain whether one draw expands into several returned records.Required. Safe integer; minimum 1; maximum 32.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
casesCasesRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 32.
cases[].mutationMutationRequired. Text; maximum UTF-16 length 65536.
cases[].jsonJsonRequired. Text; maximum UTF-16 length 65536.
cases[].startFoundStart FoundRequired. Boolean.
cases[].startValueStart ValueRequired. Text; maximum UTF-16 length 65536.
cases[].startErrorStart ErrorRequired. Text; maximum UTF-16 length 65536.
cases[].displayValidDisplay ValidRequired. Boolean.
cases[].iconsPresentIcons PresentRequired. Boolean.
cases[].themeIsStringTheme Is StringRequired. Boolean.
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": {
    "template": {
      "startUrl": "/app",
      "display": "standalone",
      "themeColor": "#123456",
      "iconSources": [
        "/icon.png"
      ]
    },
    "mutations": [
      "remove-start",
      "invalid-display"
    ],
    "count": 1,
    "seed": 42
  },
  "output": {
    "cases": [
      {
        "mutation": "invalid-display",
        "json": "{\"start_url\":\"/app\",\"display\":\"synthetic-invalid\",\"theme_color\":\"#123456\",\"icons\":[{\"src\":\"/icon.png\"}]}",
        "startFound": true,
        "startValue": "/app",
        "startError": "",
        "displayValid": false,
        "iconsPresent": true,
        "themeIsString": true
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • These labels cover particular members and parser behavior rather than complete installability or Web App Manifest conformance. The generator does not fetch icons, resolve an application environment or install a manifest.
  • 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 Web Manifest Mutation Corpus Generator — tool.io

  2. Calculation or validation: web/manifest-start-url-extractor — tool.io

  3. Calculation or validation: web/manifest-display-validator — tool.io

Similar or alternative tools

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

  • Random HTML Boolean Attribute Fixture Generator

    Construct supported Boolean-attribute spellings with lexical parser outputs, separate presence-based interpretation and author-spelling keys, including the nonconforming false-value control.