JUnit XML Failure Groups — Exact Evidence
Pricing
$100.00 / 1,000 complete junit reports
JUnit XML Failure Groups — Exact Evidence
Review repeated failure and error evidence across supported JUnit XML documents. Get test outcomes, exact fingerprints and occurrence evidence in one report for developer or agent triage. No fuzzy grouping, root-cause diagnosis, test execution or URL fetching.
Pricing
$100.00 / 1,000 complete junit reports
Rating
0.0
(0)
Developer
Picknotes
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
18 hours ago
Last modified
Categories
Share
JUnit Failure Groups
Group exact failure and error evidence from authorized JUnit XML offline. Inspect test outcomes and exact fingerprints across a bounded array of documents. No CI or test execution, issue posting, file includes or URL fetching.
Input and limits
Use {"useDemo":true} for two fictional XML documents. Expected report: five tests (one passed, two failed, one errored, one skipped), three occurrences and two groups.
Own mode requires useDemo=false, authorizedNonpersonalNonconfidentialData=true and xmlDocuments, an array of 1–16 literal XML strings. Omit own fields in demo. Generated names input-001.xml through input-016.xml reflect array order, never filesystem paths.
Strict UTF-8 only, with optional consistent UTF-8 BOM. An XML declaration may be absent or specify UTF-8 case-insensitively. DTDs, entities, namespaces, processing instructions, unsupported roots/attributes and inconsistent counts are rejected. This is a supported JUnit profile, not universal dialect support; there is no fuzzy grouping mode or redaction.
Limits: 1 MiB aggregate decoded UTF-8 input, 16 files, depth 64, 10,000 elements, 1,000 combined native records, 1,200,000 raw request bytes, 2 MiB native report and 4,500,000 serialized delivery bytes. Unsupported, invalid or incomplete output is not delivered as a partial paid report. Output is never truncated to force delivery.
Price and completed reports
US$0.10 per complete report, including the synthetic demo. Platform usage is included; no startup charge. Configure a run spending limit of at least US$0.11.
One full default-dataset item is attempted. If Apify accepts it, a completion charge can occur even if the run later fails or its acknowledgement is lost. Never automatically rerun uncertain delivery. The embedded receipt describes expected accounting, not settled charges or revenue.
Data and report download
Submit only authorized, nonpersonal, nonconfidential data. No credentials, tokens or secrets. Apify stores input before execution; reports retain XML attributes, property values, test identities, failure text, stdout/stderr and nested literal evidence. No anonymization, secret detection, deletion, private storage or retention-period promise is made.
Download the full raw default-dataset JSON without cleaning, field selection, flattening or unwinding. The matching minimal helper validates one report item or a singleton array and writes exact REPORT.json bytes:
python3 -B extract_report.py dataset.json new-output-directory
Use a new directory under an existing trusted POSIX parent. Symlink paths and overwriting existing destinations are unsupported. Python standard library only; Windows unsupported. A late filesystem failure may leave an incomplete new directory. Hash/structure checks do not authenticate the sender or prove input truth. Read the included README.md and TERMS.md; no additional support or refund promise is made here.
Helper: junit-report-helper-0.1.4.zip, 8,627 bytes, SHA-256 aaf467b2b8a59475cfa4fcec0ad231c254a885ee8346c0bd840c8911e26f14a1. Unpack all four files.
