Number of items completed.
Tracks how many items have been successfully processed so far in the current operation. This value increments as each item is completed, providing real-time progress indication.
The ratio of completed to total gives the completion percentage:
progress = (completed / total) * 100
Timestamp when the event was created.
ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.
Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")
A unique identifier for the event.
List of reviewed and validated test scenarios for the target endpoints.
Each scenario has undergone review for quality, correctness, and completeness. The scenarios include validated test scenarios, confirmed dependency functions, and any refinements made during the review process. These represent production-ready test cases that have passed validation.
Current step in the test generation workflow.
Tracks progress through the test creation process, helping coordinate with other pipeline stages and maintain synchronization with the current requirements iteration.
Detailed token usage metrics for the current operation.
Contains comprehensive token consumption data including total usage, input token breakdown with cache statistics, and output token categorization by generation type. This component-level tracking enables precise analysis of resource utilization for specific agent operations such as schema generation, test writing, or code implementation.
The token usage data helps identify optimization opportunities, monitor operational costs, and ensure efficient use of AI resources throughout the automated backend development process.
Total number of items to process.
Represents the complete count of operations, files, endpoints, or other entities that need to be processed in the current workflow step. This value is typically determined at the beginning of an operation and remains constant throughout the process.
Used together with the completed field to calculate progress percentage
and estimate time to completion.
Unique identifier for the event type.
A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.
Examples: "analyzeWrite", "prismaSchema", "interfaceOperation", "testScenario"
Event fired when the Test agent completes reviewing and validating generated e2e test scenarios.
This event occurs after the Test agent has analyzed the initially generated test scenarios, performed quality checks, validation, and potential refinements. The event provides visibility into the review process results and the finalized structure of test scenarios that have passed validation.
Each reviewed scenario includes validated test scenarios, confirmed dependency chains, and quality assurance checks to ensure the test cases are robust and ready for execution in the testing pipeline.
Author
Michael