Member Junction
    Preparing search index...

    Class AITestHarnessDialogComponent

    Dialog wrapper component for the AI Agent Test Harness. Provides a modal dialog interface with proper sizing, header, and close functionality. Automatically loads agent data and initializes the test harness with provided configuration.

    • Automatic Agent Loading: Loads agent by ID or uses provided entity
    • Configurable Dimensions: Supports custom dialog sizing
    • Initial Data Setup: Pre-populates data context and template variables
    • Clean Dialog Interface: Professional header with close button
    • Responsive Layout: Adapts to content and screen size

    This component is typically opened through the TestHarnessDialogService rather than directly:

    const dialogRef = this.testHarnessService.openAgentTestHarness({
      agentId: 'agent-123',
      initialDataContext: { userId: 'user-456' }
    });

    Hierarchy (View Summary)

    Implements

    • OnInit
    • AfterViewInit
    Index

    Constructors

    constructor

    Properties

    agent closeDialog data mode prompt Provider testHarness title ɵdir ɵfac

    Accessors

    ProviderToUse RunQueryToUse RunReportToUse RunViewToUse

    Methods

    close ngAfterViewInit ngOnInit

    Constructors

    Properties

    agent: MJAIAgentEntityExtended | null = null

    The loaded AI agent entity for testing

    closeDialog: EventEmitter<void> = ...

    Event emitted when the dialog should be closed

    data: AITestHarnessDialogData = {}

    Configuration data passed from the dialog service

    mode: "agent" | "prompt" = 'agent'

    The mode of operation - either 'agent' or 'prompt'

    prompt: MJAIPromptEntityExtended | null = null

    The loaded AI prompt entity for testing

    Provider: IMetadataProvider | null

    If specified, this provider will be used for communication and for all metadata purposes. By default, if not provided, the Metadata and RunView classes are used for this and the default GraphQLDataProvider is used which is connected to the same back-end MJAPI instance as the Metadata and RunView classes. If you want to have this component connect to a different MJAPI back-end, create an instance of a ProviderBase sub-class like GraphQLDataProvider/etc, and configure it as appropriate to connect to the MJAPI back-end you want to use, and then pass it in here.

    testHarness: AITestHarnessComponent

    Reference to the embedded test harness component

    title: string = 'AI Test Harness'

    Display title for the dialog header

    "ɵdir": unknown
    "ɵfac": unknown

    Accessors

    • get ProviderToUse(): IMetadataProvider

      Returns either the default Metadata provider or the one specified in the Provider property, if it was specified

      Returns IMetadataProvider

    • get RunQueryToUse(): IRunQueryProvider

      Returns either the default RunQuery provider or the one specified in the Provider property, if it was specified

      Returns IRunQueryProvider

    • get RunReportToUse(): IRunReportProvider

      Returns either the default RunReport provider or the one specified in the Provider property, if it was specified

      Returns IRunReportProvider

    • get RunViewToUse(): IRunViewProvider

      Returns either the default RunView provider or the one specified in the Provider property, if it was specified

      Returns IRunViewProvider

    Methods

    Settings

    Member Visibility

    On This Page

    Features:Usage:
    Constructors
    Properties
    Accessors
    Methods