Is the generated XML well-formed?

Yes. Every document starts with an XML declaration, has a single root element, properly nests child elements, and escapes the five XML special characters (& " ') in text content, so it parses cleanly in any conformant parser.

Why escape special characters?

Raw ampersands and angle brackets break XML parsing. The five predefined entities (& < > " ') must replace literal &, , double quote, and apostrophe in element content and attribute values. This tool applies that escaping automatically.

Can I use this for SOAP testing?

The records are generic rather than SOAP-enveloped, but the output is valid XML you can drop inside a SOAP body or feed to a parser. For full SOAP envelopes, wrap the generated records in your service's namespace-qualified body element.

What data types are included?

Each record includes an id attribute plus child elements for a name string, an email, an integer quantity, a decimal price, and an ISO date, giving you a mix of text, numeric, and date values to exercise type coercion in your parser.

Mock XML Generator — Gera Tools

Mock XML Generator

Legacy enterprise systems, SOAP services, and older integrations still speak XML, and testing them requires realistic, well-formed sample documents. Hand-writing XML is tedious and error-prone, especially when you need dozens of records. This tool generates a valid XML document with a configurable structure and fake typed values in one click.

How it works

The generator builds a document with an XML declaration (<?xml version="1.0" encoding="UTF-8"?>), a single root element, and a configurable number of repeated record elements. Each record carries an id attribute and a fixed set of child elements covering common data types: a name string, an email, an integer quantity, a decimal price, and an ISO 8601 date.

Crucially, all text content and attribute values are escaped against the five XML predefined entities so the result is always well-formed. Literal & becomes &, < becomes <, > becomes >, " becomes ", and ' becomes '. The whole document is assembled and indented in the browser, so nothing is sent anywhere.

Tips and notes

Validate the output by pasting it into your parser or an online XML validator; it should parse without errors.
To build a SOAP payload, wrap the generated records in your namespace-qualified <soap:Body> element.
Increase the row count to stress-test streaming parsers and memory usage on large documents.
The escaping rules here are the XML 1.0 predefined entities; CDATA sections are not used so the output stays simple and predictable.