Codex prompt

Codex Inspect: Integration Tests

Design integration coverage across boundaries with repository-aware safeguards.

Best tool
Codex
Difficulty
Advanced
Use case
Integration Tests
Prompt type
Reusable prompt

What this prompt does

Design integration coverage across boundaries with repository-aware safeguards. It is designed for integration tests and works best with Current Codex coding model configured for the repository.

Copy-ready prompt

This is a reusable natural-language prompt for Codex, not a shell command. Work in the repository at [REPOSITORY_OR_PATH]. Goal: design integration coverage across boundaries. Context: [CONTEXT]. Constraints: [CONSTRAINTS]. Definition of done: [ACCEPTANCE_CRITERIA]. Begin read-only. Trace relevant files, tests, configuration, and history before proposing changes. Read applicable AGENTS.md guidance and use Codex’s inspection, editing, and verification workflow; keep approval boundaries and the user’s working tree intact. First read the repository instructions and relevant framework documentation. Preserve unrelated user changes. State assumptions, cite files and lines for findings, and ask only when a missing decision would materially change the result. Do not invent APIs, commands, flags, test results, or file contents. Deliver: test environment, cases, cleanup, and failure diagnostics. Run the repository’s relevant formatting, lint, type, test, and build checks when authorized, and report exact results.

How to use it

Replace the bracketed variables with real context for integration tests. Attach or paste source material when available, and verify consequential facts before acting.

#codex#software-engineering#integration-tests#inspect

Related prompts