Aggregated token usage and function calling metrics by operation type.
Maps each event type within the phase to its complete aggregate metrics, including detailed token consumption breakdown with cache statistics and comprehensive function calling metrics data. This comprehensive aggregation enables deep analysis of resource utilization patterns and operation quality across the entire phase.
The partial record structure reflects that not all possible event types may occur during phase execution. Only operations that were actually performed will have entries in this mapping.
The aggregate data supports cost analysis (via token usage), reliability assessment (via function calling metrics), and optimization opportunities (via cache hit rates and failure patterns).
Results of compiling the generated e2e test TypeScript files through the TypeScript compiler.
Contains the IAutoBeTypeScriptCompileResult from processing the generated test files through the TypeScript compilation pipeline. This compilation result validates test code syntax, type safety, framework integration, and dependency resolution to ensure that all generated test scenarios are syntactically correct and ready for execution.
Through the Test agent's internal compiler feedback process, this result is typically successful as the agent iteratively refines the generated code based on compilation diagnostics. However, in rare cases where the compiler feedback iteration limit is exceeded, the result may indicate failure despite the agent's correction attempts. Such failure occurrences are extremely infrequent due to the sophisticated feedback mechanisms built into the Test agent's code generation process.
Successful compilation indicates that the generated test suite is production-ready and can be executed immediately to validate the corresponding API implementations without any syntax or integration issues.
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")
Total elapsed time for the phase execution in milliseconds.
Measures the wall-clock duration from phase start to completion, encompassing all agent operations, self-healing spiral loops, compiler validations, and any retry attempts. This metric provides visibility into phase-level performance and enables identification of bottlenecks in the waterfall pipeline.
The elapsed time includes both active LLM processing and any overhead from compilation, validation, and orchestration logic. For detailed breakdown of time spent in specific operations, consult the individual operation events within the phase.
Generated e2e test files as key-value pairs representing the complete test suite.
Contains the final set of TypeScript test files with each key representing the file path and each value containing the actual test code. Each test file includes standalone functions that implement specific use case scenarios for API endpoints, providing comprehensive end-to-end testing coverage that validates both technical functionality and business logic implementation.
The test files are designed to work under realistic operational conditions, ensuring that the generated APIs not only compile and execute correctly but also properly implement the business requirements and handle edge cases appropriately. These tests serve as both validation tools and documentation of expected system behavior.
A unique identifier for the event.
Final state machine step counter value for the phase.
Records the terminal step number from the phase's state machine, which increments monotonically during execution and invalidates cached state when operations need to be redone. This step counter enables the frontend to detect when previously completed operations have been invalidated by spiral loop corrections, ensuring UI consistency with the actual generation state.
The step value provides a temporal marker for the phase completion, allowing correlation with intermediate operation events that share the same step number.
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 the e2e test code generation process for all API endpoints and scenarios.
This event represents the successful completion of comprehensive test suite creation that validates both technical functionality and business rule implementation across all API operations. The Test agent's completion ensures that every API endpoint has multiple use case scenarios implemented as test programs that provide thorough coverage of the application functionality.
The completion of test generation creates a robust validation framework that ensures the generated APIs work correctly under realistic operational conditions and properly implement all business requirements established in the analysis phase.
Author
Samchon