# JUnit XML Failure Groups — Exact Evidence (`immemorial_sarinda/junit-failure-groups`) Actor

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.

- **URL**: https://apify.com/immemorial_sarinda/junit-failure-groups.md
- **Developed by:** [Picknotes](https://apify.com/immemorial_sarinda) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 complete junit reports

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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](https://api.apify.com/v2/key-value-stores/f7yuJ759tlYrp43zi/records/junit-report-helper-0.1.4.zip), 8,627 bytes, SHA-256 `aaf467b2b8a59475cfa4fcec0ad231c254a885ee8346c0bd840c8911e26f14a1`. Unpack all four files.

# Actor input Schema

## `authorizedNonpersonalNonconfidentialData` (type: `boolean`):

Own mode requires true for authorized, nonpersonal, nonconfidential data.

## `useDemo` (type: `boolean`):

Run bundled synthetic fixtures using the real engine. All own-data fields must be absent.

## `xmlDocuments` (type: `array`):

Own mode only; literal authorized text, never a URL. Leave absent in demo. Runtime enforces byte, structure and aggregate bounds. Supply1–16 strings, aggregate at most1MiB UTF-8.

## Actor input object example

```json
{
  "authorizedNonpersonalNonconfidentialData": false,
  "useDemo": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "useDemo": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("immemorial_sarinda/junit-failure-groups").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "useDemo": True }

# Run the Actor and wait for it to finish
run = client.actor("immemorial_sarinda/junit-failure-groups").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "useDemo": true
}' |
apify call immemorial_sarinda/junit-failure-groups --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,immemorial_sarinda/junit-failure-groups"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/aB7q0fQSL6ZXaw0he/builds/LQaAWADZuOt9T15VR/openapi.json