# How to Run Ponytail Correctness and Behavior Tests > Easily run Ponytail correctness and behavior tests with npm test or a specific node command. Learn how to execute core benchmarks for your project. - Repository: [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail) - Tags: testing - Published: 2026-08-28 --- **Run `npm test` from the repository root to execute Ponytail’s correctness and behavior tests, or use `node --test tests/correctness.test.js tests/behavior.test.js` to run only the core benchmarks without extension suites.** Ponytail is an open-source evaluation framework from DietrichGebert/ponytail that benchmarks Large Language Model outputs against reference implementations. The repository includes automated test suites that validate both algorithmic correctness and runtime behavior heuristics. Understanding how to run ponytail correctness and behavior tests ensures your local development environment matches the expected validation criteria before submitting changes. ## Running the Full Test Suite The standard entry point for validation is the **npm test** script defined in [`package.json`](https://github.com/DietrichGebert/ponytail/blob/main/package.json). This command initiates the **Node test runner** and executes all files matching the `tests/*.test.js` pattern. When you run the following from the repository root: ```bash npm test ``` The script expands to execute: ```bash node --test tests/*.test.js && npm test --prefix pi-extension && npm test --prefix ponytail-mcp ``` This runs the core correctness and behavior tests plus additional extension suites for the Pi Extension and Ponytail MCP components. ## Running Only Core Correctness and Behavior Tests To execute exclusively the two primary benchmarks without the extension suites, invoke the **Node test runner** directly with specific file paths: ```bash node --test tests/correctness.test.js tests/behavior.test.js ``` This command limits execution to: - **[`tests/correctness.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/correctness.test.js)** – Algorithmic validation tests - **[`tests/behavior.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/behavior.test.js)** – Heuristic behavior validation tests ## Understanding the Test Files Ponytail separates validation logic into distinct benchmark categories. ### Correctness Tests ([`tests/correctness.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/correctness.test.js)) The **correctness benchmark** verifies that generated implementations match reference behavior. According to the source code in [`tests/correctness.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/correctness.test.js), this includes: - **Email validation** logic - **Debounce implementation** accuracy - **CSV sum calculations** - **React countdown** component behavior - **Rate-limiting** algorithms These unit tests ensure functional equivalence between LLM outputs and ground-truth implementations. ### Behavior Tests ([`tests/behavior.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/behavior.test.js)) The **behavior benchmark** evaluates **heuristic graders** that analyze code without full execution. As implemented in [`tests/behavior.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/behavior.test.js), these tests verify that Ponytail’s runtime-level heuristics correctly assess implementation quality and predict execution characteristics. ## What the Tests Validate When you run ponytail correctness and behavior tests, the suite performs two distinct validation layers: 1. **Correctness checks** – Functional unit tests confirming that implementations (email validators, debouncers, CSV parsers, React components, rate limiters) produce expected outputs for given inputs. 2. **Behavior checks** – Runtime analysis verifying that Ponytail’s internal heuristics accurately predict code quality and execution characteristics. Both test categories execute via the native Node.js test runner introduced in recent Node versions, requiring no external test frameworks like Jest or Mocha. ## Summary - Execute `npm test` to run the complete validation suite including core tests and extension packages. - Use `node --test tests/correctness.test.js tests/behavior.test.js` for isolated testing of the primary benchmarks. - **Correctness tests** in [`tests/correctness.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/correctness.test.js) validate algorithmic implementations including email validation, debounce logic, CSV processing, React components, and rate limiting. - **Behavior tests** in [`tests/behavior.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/behavior.test.js) verify heuristic grading functionality. - Both suites run via the native **Node test runner** as configured in the repository’s [`package.json`](https://github.com/DietrichGebert/ponytail/blob/main/package.json). ## Frequently Asked Questions ### What is the difference between `npm test` and running `node --test` directly? The `npm test` command executes the full pipeline defined in [`package.json`](https://github.com/DietrichGebert/ponytail/blob/main/package.json), which includes the core tests plus extension tests for `pi-extension` and `ponytail-mcp` directories. Running `node --test` with specific file paths limits execution to only the core **correctness** and **behavior** benchmarks, making it faster for local development when you only need to validate the main algorithms. ### What specific functionality do the correctness tests cover? The **correctness benchmark** in [`tests/correctness.test.js`](https://github.com/DietrichGebert/ponytail/blob/main/tests/correctness.test.js) validates five primary implementation categories: email address validation rules, debounce timing mechanisms, CSV numerical aggregation, React countdown timer components, and request rate-limiting algorithms. These tests ensure that generated code produces mathematically and logically correct outputs. ### Do I need to install external testing frameworks to run these tests? No. Ponytail uses the native **Node test runner** available in modern Node.js versions. The repository relies on the built-in `node --test` CLI functionality rather than third-party libraries like Jest or Mocha, eliminating additional dependencies beyond the Node runtime itself. ### Can I run individual test files separately? Yes. You can target specific benchmarks by passing individual file paths to the Node test runner. For example, `node --test tests/correctness.test.js` runs only the algorithmic validation suite, while `node --test tests/behavior.test.js` executes only the heuristic behavior checks. This granular control helps debug specific failure categories without running the entire suite.