<a id="dads-testing-native-runtime-windows-x64"></a>

# Dads Testing native runtime (Windows x64)

This package contains the platform-native `dad-test.exe` executable used by `@dads-framework/testing` on Windows x64.

<a id="try-it"></a>

## Try it

Use PowerShell and Node.js 22 or newer in an empty directory on Windows x64. Normally, npm selects this runtime when you install [`@dads-framework/testing`](https://dadsframework.dev/docs/package-testing). Use this direct install after the public release when optional dependencies are unavailable.

```powershell
node -p 'process.platform + "-" + process.arch'
npm init -y
npm install --save-dev @dads-framework/testing-native-win32-x64
$binary = node -p 'require.resolve("@dads-framework/testing-native-win32-x64")'
$binary
Test-Path -LiteralPath $binary -PathType Leaf

@'
{
  "schemaVersion": 1,
  "workspace": { "root": ".", "fullFallback": { "taskIds": ["app:test"] } },
  "projects": [{ "id": "app", "root": ".", "fallbackDependencies": [] }],
  "tasks": [{
    "id": "app:test",
    "project": "app",
    "kind": "test",
    "execution": { "executable": "node", "args": ["--version"], "cwd": "." },
    "dependsOn": [],
    "impact": { "mode": "always" }
  }]
}
'@ | Set-Content -Encoding ascii dads.testing.json
node -p 'JSON.stringify({ schemaVersion: 1, operation: "plan", workspaceRoot: process.cwd(), all: true })' | & $binary
```

The host check prints `win32-x64`. The binary path ends in `bin\dad-test.exe`, followed by `True` from the file check. The native response contains `"ok":true` and a task with `"id":"app:test"` and `"decision":"run"`. A plan shows which tasks would run.

In the repository, the [native release workflow](https://dadsframework.dev/docs/source/.github/workflows/testing-native-release.yml) packs this platform's package from `packages/testing/native/win32-x64/` and installs the tarball with the facade in a fresh `testing-consumer` directory to check planning through the installed artifact.

<a id="commands"></a>

## Commands

The native executable reads one JSON request from standard input. Set `workspaceRoot` to an absolute directory containing `dads.testing.json`. It accepts `plan` and `run` as the `operation` field. For the flag-based CLI, including `init` and `explain`, use the [testing facade](https://dadsframework.dev/docs/package-testing#commands).

<a id="what-it-refuses-to-do"></a>

## What it refuses to do

This build supports Windows x64 only.

<a id="contract"></a>

## Contract

The executable returns a JSON response with `schemaVersion` and `ok`. On success, `result.plan` describes task selection. An invalid request returns `ok: false`, an `error` message, and exit code 1. Use the [testing facade](https://dadsframework.dev/docs/package-testing#contract) for the supported application interface.

Canonical page: <https://dadsframework.dev/docs/package-testing-native-win32-x64>
