IMPORTANT: Transition to AI Agent Reporting
The TypeScript/JavaScript SDK is no longer the primary method within AskUI. It is now the previous generation. This means manual integration of Jest reporters is an obsolete method. We strongly recommend switching automation logic to the Python SDK to leverage the automated reporting capabilities of the Caesr.ai AI Agent platform. Stop writing repetitive configuration files and manual image handling code.
The Old Problem: Heavy Manual Configuration
To generate useful reports (XML, HTML) with the legacy system, developers had to:
- Install multiple separate
npmpackages likejest-junit,jest-html-reporters. - Manually configure the
jest.config.tsfile to include these reporters. - Write complex TypeScript code to manually process screenshots which converting base64 strings to buffers just to attach them to a report.This process required significant effort to maintain the reporting pipeline.
The New Solution: Automated Reporting with Caesr.ai
Caesr.ai transforms reporting from a manual configuration burden into a default, automated feature.
1. Instant, Rich Reporting
Every workflow executed by the Caesr.ai AI Agent automatically generates a rich report. This report inherently includes:
- Detailed steps of the AI Agent's execution.
- Screenshots for every single action performed by the Agent.
- Assertions and final pass/fail status.
This eliminates the need for any Jest reporter packages, manual configuration files, or buffer processing code.
2. Primary Language Focus
We strongly recommend utilizing the Python SDK which is AskUI's primary language. The system includes native support for Pytest and other common test runners which provides users with sophisticated reporting capabilities and CI/CD integration without requiring them to handle the complex TypeScript/Jest toolchain from previous versions.
Reporting Becomes Automated, Not Configured
The time spent managing jest.config.ts files and manually converting images is over. The implementation of Caesr.ai enables reporting to transition from its current state as a delicate custom setup process into an automated standard function which enables your team to concentrate on automation development instead of reporter configuration.

