Random HTML Text Extraction Corpus Generator

Description

Compose bounded escaped paragraph/span/emphasis, comment, inert-script, and comment-only-style source from supplied text, then delegate text extraction, tag stripping, and comment removal separately; retain raw source and entity conventions without executing markup/scripts, browser layout equivalence, or sanitization claims.

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.

When to use this tool

Use this generator to create reproducible html text extraction 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

Supply texts, kinds, caseCount, fragmentsPerCase 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 cases. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Encode supplied text and wrap it in sampled normal elements, comments, inert script, or style fragments. Delegate text extraction, tag stripping, and comment removal, independently checking their deliberately different expected outputs.^[1]

Delegated operations used for this result: text extractor; tag stripper. Their calculation or parsing conventions apply to the corresponding result fields.^{[2, 3]}

Input field	Meaning and units	Accepted input
texts	Texts	Required. Array of Text; maximum UTF-16 length 64.; minimum items 1; maximum items 16.
kinds	Kinds	Required. Array of Text; one of "paragraph", "span", "emphasis", "comment", "inert-script", "style-comment".; minimum items 1; maximum items 6.
caseCount	Case Count	Required. Safe integer; minimum 1; maximum 16.
fragmentsPerCase	Fragments Per Case	Required. Safe integer; minimum 1; maximum 16.
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
cases	Cases	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 16.
cases[].fragments	Fragments	Required. Array of Object; no unknown keys.; minimum items 1; maximum items 16.
cases[].fragments[].kind	Kind	Required. Text; one of "paragraph", "span", "emphasis", "comment", "inert-script", "style-comment".
cases[].fragments[].text	Text	Required. Text; maximum UTF-16 length 64.
cases[].fragments[].body	Body	Required. Text; maximum UTF-16 length 400.
cases[].fragments[].source	Source	Required. Text; maximum UTF-16 length 512.
cases[].html	Html	Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
cases[].extractedText	Extracted Text	Required. Text; maximum UTF-16 length 8192.
cases[].tagStrippedText	Tag Stripped Text	Required. Text; maximum UTF-16 length 8192.
cases[].commentsRemovedHtml	Comments Removed Html	Required. Text; maximum UTF-16 length 8192.
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.

json

{
  "input": {
    "texts": [
      "A&B",
      "x<y"
    ],
    "kinds": [
      "paragraph",
      "comment",
      "inert-script",
      "span"
    ],
    "caseCount": 1,
    "fragmentsPerCase": 4,
    "seed": 42
  },
  "output": {
    "cases": [
      {
        "fragments": [
          {
            "kind": "inert-script",
            "text": "A&B",
            "body": "A&amp;B",
            "source": "<script type=\"text/plain\">A&amp;B</script>"
          },
          {
            "kind": "span",
            "text": "x<y",
            "body": "x&lt;y",
            "source": "<span>x&lt;y</span>"
          },
          {
            "kind": "paragraph",
            "text": "x<y",
            "body": "x&lt;y",
            "source": "<p>x&lt;y</p>"
          },
          {
            "kind": "comment",
            "text": "x<y",
            "body": "x&lt;y",
            "source": "<!-- x&lt;y -->"
          }
        ],
        "html": "<script type=\"text/plain\">A&amp;B</script><span>x&lt;y</span><p>x&lt;y</p><!-- x&lt;y -->",
        "extractedText": "x<yx<y",
        "tagStrippedText": "A&amp;Bx&lt;yx&lt;y",
        "commentsRemovedHtml": "<script type=\"text/plain\">A&amp;B</script><span>x&lt;y</span><p>x&lt;y</p>"
      }
    ],
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

The linked operations are lexical tools rather than browser DOM rendering or sanitization. Generated markup is test data and must be displayed as escaped code, especially script and style fragments.
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

Tool behavior and example: Random HTML Text Extraction Corpus Generator — tool.io
Calculation or validation: html/text-extractor — tool.io
Calculation or validation: html/tag-stripper — 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.