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.
When to use ipc_tests_run
Use ipc_tests_run 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 inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Optional
modeenumsmokefullbenchmarkstress+2 moreTest mode to run. Options: 'smoke' (quick validation, 5 tests), 'full' (comprehensive, 138+ tests), 'benchmark' (performance testing), 'stress' (load testing), 'leak-check' (memory leak detection), 'parallel' (concurrent context testing). Default: 'full'
verbosebooleanEnable verbose output during test execution. Default: false
iterationsintegerNumber of iterations for benchmark mode. Default: 1
contextsintegerNumber of browser contexts for stress mode. Default: 10
durationintegerDuration in seconds for stress and leak-check modes. Default: 60
concurrencyintegerNumber of concurrent threads for parallel mode. Default: 1
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does ipc_tests_run do?
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. It belongs to Owl Browser's IPC Testing category and is available through the REST API, the Python SDK (browser.ipc_tests_run()), the Node.js SDK, and the MCP server.
What parameters does ipc_tests_run accept?
ipc_tests_run accepts 0 required parameters and 6 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/ipc_tests_run.
Is ipc_tests_run detectable by anti-bot systems like Cloudflare or DataDome?
No. ipc_tests_run 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_statusGet 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_abortAbort 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_list_reportsList 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.
ipc_tests_get_reportGet 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_reportDelete 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_allDelete all IPC test reports. Removes all JSON, HTML, and log files from the reports directory. Use to clean up all test history.