# How to Run the Agent-Reach Tests: Unit and Integration Validation > Learn how to run Agent-Reach tests easily. Validate core logic and end-to-end channel functionality with pytest unit tests and the test.sh integration suite. - Repository: [Pnant/Agent-Reach](https://github.com/Panniantong/Agent-Reach) - Tags: how-to-guide - Published: 2026-06-18 --- **Agent-Reach provides two testing layers—unit tests via pytest in the `tests/` directory and a full integration suite via the [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) bash script—that validate everything from core Python logic to end-to-end channel functionality.** The Panniantong/Agent-Reach repository ships with a comprehensive testing strategy to ensure reliability across its multi-platform agent framework. Whether you are contributing code or verifying a local installation, knowing how to run the Agent-Reach tests is essential for confirming that channels, CLI commands, and configuration handlers work correctly. ## Running the Unit Test Suite The fastest way to validate core logic is through the **unit tests** located in the `tests/` directory. These pure Python tests exercise components like [`agent_reach/core.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/core.py), CLI argument parsing in [`agent_reach/cli.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/cli.py), and channel contract enforcement without requiring network calls or external credentials. First, install the package in editable mode: ```bash pip install -e . ``` Then execute the test runner with verbose output: ```bash pytest tests/ -v ``` This command discovers all files matching `test_*.py` and prints individual test results, covering modules such as [`test_cli.py`](https://github.com/Panniantong/Agent-Reach/blob/main/test_cli.py), [`test_core.py`](https://github.com/Panniantong/Agent-Reach/blob/main/test_core.py), and [`test_channels.py`](https://github.com/Panniantong/Agent-Reach/blob/main/test_channels.py). ## Running the Full Integration Test For end-to-end validation, use the **integration test** orchestrated by [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) in the project root. Unlike unit tests, this bash script creates an isolated virtual environment, installs Agent-Reach from the GitHub zip distribution, and executes real commands against live platforms including web, GitHub, YouTube, BiliBili, RSS, Twitter, and Reddit. Execute the integration suite: ```bash bash test.sh ``` The script performs the following sequence: 1. Creates a temporary directory and fresh Python virtual environment 2. Installs the latest `agent-reach` package from GitHub 3. Runs `agent-reach install --env=auto` to trigger automatic system-tool detection 4. Executes `agent-reach doctor` to verify channel health via [`agent_reach/doctor.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/doctor.py) 5. Fires read and search commands against all supported backends 6. Inspects output for success markers (✅, ⏭️, or ❌) ## Interpreting Test Results Understanding the output symbols ensures you can distinguish between actual failures and skipped tests. - **Pass (✅)**: The command returned a result containing a URL or expected content marker, confirming the channel backend is functional. - **Skip (⏭️)**: The command reported a missing dependency, such as a platform requiring cookies or a tool not installed in the clean environment. - **Fail (❌)**: The command raised an exception or returned unexpected output, indicating a regression in the channel logic or configuration parser. If failures occur, the script prints the first two lines of the offending command's output, which you can cross-reference with the logic in [`agent_reach/core.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/core.py) to debug routing issues. ## Manual Testing Commands During development, you may want to test specific components without running the full suites. You can manually trigger the installer and diagnostic tools: ```bash # Verify installation and environment setup agent-reach install --env=auto ``` ```bash # Run health diagnostics agent-reach doctor ``` ```bash # Test a specific read command agent-reach read 'https://example.com' ``` ```bash # Test search functionality agent-reach search 'best AI agent framework' -n 2 ``` These commands mirror the checks performed by [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) but allow targeted debugging of individual channels or CLI behaviors. ## Summary - The **unit test suite** in `tests/` uses `pytest` to validate pure Python logic quickly, including core routing in [`agent_reach/core.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/core.py) and CLI parsing in [`agent_reach/cli.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/cli.py). - The **integration test** in [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) verifies end-to-end functionality by creating a clean virtual environment and testing real network calls against all supported platforms. - Run `pytest tests/ -v` for rapid iteration during development, and `bash test.sh` before releases to ensure the full user installation path works on fresh systems. - Interpret result markers (✅, ⏭️, ❌) to distinguish between pass, skip, and fail states when analyzing integration output. ## Frequently Asked Questions ### What is the difference between unit tests and integration tests in Agent-Reach? Unit tests validate isolated Python components like configuration parsing and channel contracts without network dependencies, while the integration test in [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) validates the complete installation flow, real API calls, and the diagnostic engine in [`agent_reach/doctor.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/doctor.py) using a fresh virtual environment. ### Do I need API keys or authentication to run the tests? The unit tests require no external credentials. The integration test may skip certain platforms (marked with ⏭️) if they require authentication cookies or API keys that are not present in the clean test environment, but it will continue testing other channels. ### How do I run a specific unit test file instead of the entire suite? Target individual test modules by passing the file path to pytest: `pytest tests/test_core.py -v`. This approach is useful when debugging specific logic in [`agent_reach/core.py`](https://github.com/Panniantong/Agent-Reach/blob/main/agent_reach/core.py) without waiting for the full suite to complete. ### Why does the integration test create a new virtual environment? The [`test.sh`](https://github.com/Panniantong/Agent-Reach/blob/main/test.sh) script isolates the test run from your development environment to ensure no leftover packages or configuration files mask installation failures. This verifies that a new user cloning the Panniantong/Agent-Reach repository can successfully install and run the tool from scratch.