code-review-testing

Guide integration tests for codex agent changes using test_codex in core/suite.

4|1|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/xrehpicx/anya --skill code-review-testing-xrehpicx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-testing
Source: https://github.com/xrehpicx/anya/tree/main/.codex/skills/code-review-testing
Command: npx skills add https://github.com/xrehpicx/anya --skill code-review-testing-xrehpicx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps teams structure tests for agent changes by prioritizing integration tests over unit tests and providing a clear workflow for test planning and validation.

Core Features & Use Cases

  • Integration-test-first guidance: prefer integration tests under core/suite using test_codex to verify end-to-end behavior.
  • Clear routing for unit tests: place unit tests in dedicated *_tests.rs and avoid test-only functions in the main implementation.
  • Helpers and readability: encourage reuse of existing test utilities to keep tests concise and maintainable.

Quick Start

Start by creating an integration test in core/suite using test_codex to verify the new feature before adding unit tests.

Frequently Asked Questions about code-review-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write integration tests for codex agent changes?

Write integration tests for codex agent changes by placing them in the core/suite directory and using the test_codex utility to verify end-to-end behavior before release.

When should I use integration tests versus unit tests for agent logic?

Prioritize integration tests in core/suite for major agent logic changes to verify end-to-end behavior, and route unit tests to dedicated *_tests.rs files for granular validation.

Where should I place unit tests to avoid test-only functions in the main implementation?

Place unit tests in dedicated *_tests.rs files to avoid test-only functions in the main implementation, ensuring the primary codebase remains clean and production-ready.

What is the recommended testing workflow for codex agent features?

Start the codex agent testing workflow by creating an integration test in core/suite using test_codex to verify new behavior, then add unit tests in dedicated *_tests.rs files.

Are integration tests required for all agent logic modifications?

Integration tests are required for major agent logic modifications to verify behavior before release, while smaller changes can rely on unit tests placed in dedicated *_tests.rs files.

How do I keep test utilities readable and maintainable for agent changes?

Keep test utilities readable and maintainable for agent changes by reusing existing test helpers instead of duplicating logic, ensuring tests remain concise and easy to manage.