Member Junction
    Preparing search index...

    Interface DriverExecutionResult

    Result from driver execution

    interface DriverExecutionResult {
        actualOutput?: unknown;
        allAgentRunIds?: string[];
        durationMs?: number;
        errorMessage?: string;
        expectedOutput?: unknown;
        failedChecks: number;
        inputData?: unknown;
        oracleResults: OracleResult[];
        outputs?: TestRunOutputItem[];
        passedChecks: number;
        score: number;
        skippedChecks?: number;
        status: "Passed" | "Failed" | "Skipped" | "Error" | "Timeout";
        targetLogEntityId?: string;
        targetLogId: string;
        targetType: string;
        totalChecks: number;
        totalCost?: number;
        totalTurns?: number;
        turnResults?: TurnResult[];
    }
    Index

    Properties

    actualOutput? allAgentRunIds? durationMs? errorMessage? expectedOutput? failedChecks inputData? oracleResults outputs? passedChecks score skippedChecks? status targetLogEntityId? targetLogId targetType totalChecks totalCost? totalTurns? turnResults?

    Properties

    actualOutput?: unknown

    Actual output data

    allAgentRunIds?: string[]

    Multi-turn specific: All AgentRun IDs

    durationMs?: number

    Duration in milliseconds

    errorMessage?: string

    Error message if status is Error

    expectedOutput?: unknown

    Expected output data

    failedChecks: number

    Number of checks that failed

    inputData?: unknown

    Input data used

    oracleResults: OracleResult[]

    Oracle results

    outputs?: TestRunOutputItem[]

    Structured outputs emitted by the driver (screenshots, logs, data, etc.). The engine persists each item as a TestRunOutput entity record.

    passedChecks: number

    Number of checks that passed

    score: number

    Overall score

    skippedChecks?: number

    Number of checks that were skipped (tier-gated, mutation-gated, or environment gaps). Optional so existing drivers that never skip need no change.

    status: "Passed" | "Failed" | "Skipped" | "Error" | "Timeout"

    Execution status. 'Skipped' means the driver did not execute the test's checks at all (env-gated tier, unreachable dependency) — it must NEVER be reported as 'Passed': a green run that silently didn't execute is indistinguishable from real coverage. The MJ: Test Runs entity's Status value list already includes 'Skipped'.

    targetLogEntityId?: string

    Entity ID identifying the type of target being tested. References Entity.ID (e.g., Entity ID for "MJ: AI Agent Runs"). This is the proper FK reference for entity linkage.

    targetLogId: string

    Target entity ID (final AgentRun ID for single/multi-turn)

    targetType: string

    Optional sub-category or variant label for the test target. Use for ad-hoc labeling or to distinguish test scenarios within the same entity type. Examples: "Summarization", "Classification", "Code Review", "Multi-turn Chat"

    totalChecks: number

    Total number of checks EXECUTED (passed + failed). Skipped checks are counted separately in skippedChecks and never inflate the executed totals.

    totalCost?: number

    Cost in USD

    totalTurns?: number

    Multi-turn specific: Total number of turns

    turnResults?: TurnResult[]

    Multi-turn specific: Results for each turn

    Settings

    Member Visibility

    On This Page

    Properties