platform

Platform runner profiles (experimental)

Build constructs fixed arguments; Parse decodes original native observations. Neither admits an executable, proves dependency closure, maps assertions to an accepted criterion, or authorizes application/device changes. The caller uses the shared executor with independently pinned tools, configuration and source inputs.

Sixteen concrete profiles exist:

Full negative, retry, platform/version and lifecycle qualification remains open. Fixtures and parser tests are not substitutes for those required live witnesses. Appium and domain-specific SQL/shader/HTML/data runner IDs remain explicit unavailable obligations; they are not removed from release scope. SwiftPM XCTest uses the serial native text protocol because its parallel XML writer reported a skipped case as an ordinary passing testcase. Kotlin JS/native, Apple UI/device and physical Android device variants are not qualified by the JVM/macOS/local-emulator rows.

Invocation details and authority limits

Gradle requires one literal project directory, its pinned build.gradle or build.gradle.kts, a fully qualified task path such as :test, and pinned Java. A fixed init script selects that native Test task, forces a fresh XML location, disables up-to-date reuse, and rejects no-match selection. Selectors require a fully package-qualified class and method with a non-uppercase package prefix; Gradle's uppercase simple-class shortcuts can otherwise match multiple packages. Project plugins and other task/configuration code remain trusted local dependencies. Any reported retry extension or duplicate identity refuses until a retry profile is qualified.

Maven requires the project's pinned pom.xml, pinned Java and optionally a pinned settings XML in Reporter. The POM must set Surefire reportsDirectory to ${corvint.reportsDirectory}. Surefire has no equivalent user property to force this setting. Missing wiring produces absent fresh reports and refusal; old target reports are never imported. The fixed invocation is offline, requires tests and sets surefire.rerunFailingTestsCount=0. Project plugin behavior and other POM execution remain explicit caller dependencies. JAVA_HOME is derived from the independently pinned Java executable for both launcher profiles.

Kotlin JVM profiles load the independently pinned Console jar and a literal compiled-classes directory with its prepared runtime jars. Full artifact closure is a separate input obligation. Kotlin-test selectors are exact class#method or native unique IDs; Kotest selectors are native unique IDs. Reports retain full engine/spec/test identity, including native parameter/nesting segments.

Android profiles execute only an explicit local emulator-NNNN serial and the literal package/androidx.test.runner.AndroidJUnitRunner component. They never install APKs, clear data or grant permissions. APK identity, existing adb server, emulator image, application state and SDK dependencies remain caller admission and qualification obligations. Adb exit zero is outcome-neutral: native per-test start/terminal records, ordinal/count consistency, aggregate summary and final instrumentation code determine observed outcomes. A native exception without recognized assertion evidence remains UNKNOWN failure kind. Espresso and UIAutomator sharing this transport does not imply they share semantic coverage.

Aggregate outcomes retain failure kind/message without fabricated attempts. Native retry history stays NOT_REPORTED unless actually available. A complete report means complete observed inventory, never full expected-selector coverage, criterion acceptance, mutation kill or Tasks completion.

Actual raw reports, source fixtures, APK checksums, runtime versions and launcher transcripts are retained in /private/tmp/cem10-build/platform during the build. See testdata/README.md for fixture normalization and provenance.

SwiftPM XCTest requires the selected package's pinned Package.swift and exact Module.Class/testMethod selectors. The qualified serial macOS protocol validates case lifecycle, suite nesting, failure-event counts and skipped-body counts. A setup exception can mark a body skipped while the method still fails with an infrastructure error. Linux output, retries and arbitrary custom observers remain unqualified. The Swift 6.4 --skip-update option is deprecated.

Robolectric requires prepared compiled classes/runtime jars, pinned Console jar and the exact pinned API-35 android-all-instrumented artifact for Robolectric 4.16.1. The fixed invocation sets offline mode and enabledSdks=35. Other SDKs, resource/application variants and complete dependency closure remain unqualified.