JSON ↔ XML Converter

// HOW TO USE

1. 01Pick a direction — JSON → XML or XML → JSON.
2. 02Arrays in JSON become repeated tags in XML; keys starting with @ become XML attributes, and #text becomes text content.
3. 03XML → JSON groups duplicate sibling tags into arrays and attaches attributes under @name keys.

// WHEN TO USE

Use this when integrating with SOAP APIs, legacy systems, or tools that require XML but your data is in JSON — or the reverse when you receive XML responses that need to become JSON for assertion or storage. The converter handles the structural mapping between formats: JSON arrays become repeated XML tags, XML attributes are preserved under @ keys in the JSON output. Use it to build test payloads for XML-consuming APIs and to parse SOAP responses into assertable JSON.

// WHAT BUGS THIS FINDS

• Array element tag naming

  JSON arrays produce repeated XML tags named after the parent key — if the API expects differently-named wrapper or item elements, the mismatch causes a schema validation error. Convert and review the tag structure before sending.

• XML attribute vs element handling

  An XML attribute (@id='123') becomes a @id key in JSON and vice versa — if the consumer expects an attribute but receives a child element, the mapping is wrong. Convert and inspect the tag anatomy.

• Null and empty value representation

  A JSON null maps to an empty XML tag (<field/>) in some schemas but to an attribute (xsi:nil='true') in others — Convert shows what the tool emits so you can identify schema mismatches early.

• Namespace loss in XML-to-JSON

  XML namespaces (xmlns:soap=...) are stripped or flattened during XML-to-JSON conversion — Convert and compare to confirm namespace prefixes survive for SOAP-based contract tests.

// QA USE CASES