# English/French ICU Message Regression Fixtures (`usta/localewitness-icu-regression-fixtures`) Actor

Generate English/French ICU message branch witnesses, expected output and a pseudolocale in one regression ZIP. Bounded integer profile; explicit coverage limits. One completed packet per run.

- **URL**: https://apify.com/usta/localewitness-icu-regression-fixtures.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / completed fixture packet

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## English/French ICU message regression fixtures

For localization engineers maintaining English and French message catalogs, LocaleWitness generates repeatable input cases and coverage evidence before a release. It does not translate messages or judge translation quality.

### What you receive

One ZIP with preserved source and target messages, parsed syntax, branch witnesses and expected rendered strings, a syntax-preserving pseudolocale, changes from an optional previous release, and a coverage report. Files: input.schema.json, bundle.json, witnesses.json, pseudolocale.json, release-delta.json, report.md and PROFILE.md. The completed-packet dataset row links to the ZIP and gives its SHA-256.

Inspect the report before using the fixtures. This is a bounded testing profile, not proof that a translated application is correct. Download the packet before your Apify storage retention expires.

### Input example

Set the payload field to:

```
{
  "source_locale": "en",
  "target_locale": "fr",
  "source": {
    "greeting": "Hello {name}",
    "basket": "{count, plural, =0 {Empty} one {# item} other {# items}}"
  },
  "target": {
    "greeting": "Bonjour {name}",
    "basket": "{count, plural, =0 {Vide} one {# article} other {# articles}}"
  }
}
```

### Supported scope

English and French only. Named arguments, select, plural, selectordinal, exact integer selectors, offsets, fallback branches and apostrophe quoting are supported. Numeric arguments are integers 0-999. Maximum 32 messages, 4096 UTF-8 bytes per message, 65536 message/key bytes, 8 argument names and 2048 total witnesses. max\_combinations defaults 128 and is capped at 512 per message.

Dates, times, number formatters, skeletons, decimals, locale aliases, full ICU/CLDR conformance and translation quality are outside this profile. The JSON bundle is not a compiled JavaScript library.

Incomplete combination coverage returns UNKNOWN without a completed-packet dataset row. Invalid input returns an input diagnostic. Neither is a successful packet.

### Data handling

This edition runs on Apify. Your supplied catalogs and generated files are processed and stored there under your account and Apify retention settings. Use synthetic or authorized data. Do not upload credentials or sensitive personal information. Artifact URLs may be shared: treat them as access-bearing links. This is not a local-only or permanent storage service.

### Reuse

Use the JSON witnesses in your own test runner; compare the actual application output with the declared expected strings. Keep original message IDs and review every release delta. No external messages or application changes are performed.

### Run and download

1. Review the supported input and try the included synthetic example. Replace **payload** with your authorized records. For API runs, send an object with a single payload field containing that input.
2. Run the Actor. Open **Status and coverage** to inspect the result.
3. For a completed result, open **Download completed ZIP** or the artifact link in the dataset. Save and extract the ZIP before Apify retention expires. Open the HTML report where provided; retain the JSON and CSV evidence.

### Price and unsuccessful runs

**$0.50 per completed packet**, with one packet per run and no start fee. A retry of the same run reuses the packet and the same billing identity. Starting a separate run is a separate request. Invalid input or an incomplete UNKNOWN result produces a diagnostic without a completed-packet charge. A completed conflict or shortage report can still require manual review; PASS does not mean every business problem was resolved.

The minimum run budget is $0.50. The example is a normal run and follows the same price; it is not a free preview promise. Apify handles account billing. These files are not permanent storage: download them promptly.

### Access and support

Your input and output are processed on Apify under the run owner's account. Use authorized data and opaque IDs; do not upload passwords or sensitive personal records. Treat artifact URLs as access-bearing links and share them only intentionally. The USTA report may fetch the Satoshi font; it does not upload your report. For a product issue, use this Actor's Issues tab with the run ID and a redacted example. Never post private input or access-bearing links in a public issue.

# Actor input Schema

## `payload` (type: `object`):

English/French source and target messages.32messages maximum; integer plural arguments0-999. Input is processed on Apify.

## Actor input object example

```json
{
  "payload": {
    "source_locale": "en",
    "target_locale": "fr",
    "source": {
      "greeting": "Hello {name}",
      "basket": "{count, plural, =0 {Empty} one {# item} other {# items}}"
    },
    "target": {
      "greeting": "Bonjour {name}",
      "basket": "{count, plural, =0 {Vide} one {# article} other {# articles}}"
    }
  }
}
```

# Actor output Schema

## `packet` (type: `string`):

No description

## `report` (type: `string`):

No description

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/localewitness-icu-regression-fixtures").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("usta/localewitness-icu-regression-fixtures").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 '{}' |
apify call usta/localewitness-icu-regression-fixtures --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usta/localewitness-icu-regression-fixtures"
        }
    }
}
```

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/SQh7tN9X9F9flfytR/builds/AqUzq2BGYhg42dbZl/openapi.json