Owl Browser
DocsIPC Testingipc_tests_list_reports

ipc_tests_list_reports

ipc_tests_list_reports

List all available IPC test reports. Returns an array of report metadata including run_id, timestamp, mode, test counts, and duration. Reports are stored in the reports directory.

When to use ipc_tests_list_reports

Use ipc_tests_list_reports when you need to automate a browser task. It is part of Owl Browser's IPC Testing toolset and runs inside a self-hosted, source-level stealth engine, so every call uses the same configured fingerprint controls as the rest of your automation. Detection still depends on the site, network, behavior, and profile consistency.

Usage Example

12345678910
import asyncio
from owl_browser import OwlBrowser, RemoteConfig
# Async usage
async with OwlBrowser(config) as browser:
context_id = await browser.create_context()
await browser.ipc_tests_list_reports(
)

Response

Returns a JSON object with the operation result.

{
  "success": true,
  "result": <value>
}

Frequently Asked Questions

What does ipc_tests_list_reports do?

List all available IPC test reports. Returns an array of report metadata including run_id, timestamp, mode, test counts, and duration. Reports are stored in the reports directory. It belongs to Owl Browser's IPC Testing category and is available through the REST API, the Python SDK (browser.ipc_tests_list_reports()), the Node.js SDK, and the MCP server.

What parameters does ipc_tests_list_reports accept?

ipc_tests_list_reports takes no required parameters beyond an active context. Call it with a POST request to /api/execute/ipc_tests_list_reports.

Is ipc_tests_list_reports detectable by anti-bot systems like Cloudflare or DataDome?

No. ipc_tests_list_reports executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.

Related Tools

ipc_tests_run

Start a new IPC test run to validate browser IPC communication. Supports multiple test modes: 'smoke' for quick validation (5 tests), 'full' for comprehensive testing (138+ methods), 'benchmark' for performance measurement, 'stress' for load testing, 'leak-check' for memory analysis, 'parallel' for concurrent context testing. Returns a run_id to track progress.

ipc_tests_status

Get the status of an IPC test run. Returns status (running/completed/failed/aborted), test results summary (total/passed/failed), duration, and commands per second. If run_id is not provided, returns status of the current or last run.

ipc_tests_abort

Abort a running IPC test. Sends SIGTERM to the test process and waits for graceful shutdown. Use when a test is taking too long or needs to be cancelled.

ipc_tests_get_report

Get a specific IPC test report by run_id. Returns JSON data, HTML dashboard, or raw log output depending on the format parameter. JSON includes detailed test results, latency stats, resource usage, and failure details. HTML is an interactive dashboard with charts. Log returns the test client's stdout/stderr output for debugging failures.

ipc_tests_delete_report

Delete an IPC test report by run_id. Removes JSON, HTML, and log files from disk. Use to clean up old test results.

ipc_tests_clean_all

Delete all IPC test reports. Removes all JSON, HTML, and log files from the reports directory. Use to clean up all test history.

Browse the full Owl Browser API reference or get started with the Python SDK and Node.js SDK.