test-inspector

Test Inspector

Analyze the test and simulation setup of a repository.

Input

The prompt will contain:

• REPO_PATH: absolute path to the repository

Procedure

1. Identify Test Framework

Search for test configuration and identify the framework:

Indicator	Framework
pytest.ini, conftest.py, pyproject.toml [tool.pytest]	pytest
unittest imports in test files	Python unittest
jest.config.js, jest.config.ts	Jest
vitest.config.*	Vitest
.mocharc.*, mocha in package.json	Mocha
karma.conf.js	Karma
CTestTestfile.cmake, enable_testing()	CTest
gtest includes or TEST( macros	Google Test
catch.hpp includes or TEST_CASE(	Catch2
func Test in _test.go files	Go testing
#[test] in .rs files	Rust cargo test

Also check package.json scripts for test commands, and Makefile for test targets.

2. Count Test Files and Estimate Test Count

Count test files by pattern:

• Python: test_*.py, *_test.py in tests/, test/, or anywhere
• C/C++: *_test.cpp, *_test.c, test_*.cpp, test_*.c
• JavaScript/TypeScript: *.test.js, *.test.ts, *.spec.js, *.spec.ts
• Go: *_test.go
• Rust: files containing #[test]

Estimate individual test count by grepping within test files:

• Python: count def test_ and class Test
• C/C++: count TEST(, TEST_F(, TEST_P(
• JS/TS: count it(, test( (not inside describe)
• Go: count func Test
• Rust: count #[test]

3. Search for Simulation and Benchmark Methods

Look for simulation or benchmarking infrastructure:

File name patterns: Search for files or directories containing:

• simulate, simulation, sim
• benchmark, bench, perf
• mock, fixture, fake, stub
• emulate, emulator

Directory patterns: Check for dedicated directories:

• benchmarks/, bench/
• simulation/, sim/
• perf/, performance/
• fixtures/, mocks/

Content patterns: Grep for:

• Python: @pytest.mark.benchmark, timeit, cProfile
• C/C++: benchmark::State, BENCHMARK(
• JS: performance.now(), console.time(
• General: simulate(, run_simulation(

For each found simulation/benchmark method, describe:

• What it simulates or measures
• How to run it
• What output to expect

If nothing found, state: "此仓库中未检测到仿真或基准测试方法。"

4. Analyze Test Organization

Describe how tests are organized:

• Are tests in a separate directory or co-located with source?
• Is there a test configuration file? What options are set?
• Are there test fixtures, conftest files, or shared test utilities?
• Is there CI configuration that runs tests (.github/workflows/, .gitlab-ci.yml, Jenkinsfile)?

5. Generate Test Instructions

Write step-by-step instructions to run the test suite:

1. Prerequisites (test dependencies to install)
2. Command to run all tests
3. Command to run a specific test file or test case
4. How to see test coverage (if configured)
5. How to run benchmarks/simulations (if found)

Output Format

Wrap all output between these exact markers. All section headers and field labels MUST be in Chinese as shown below. All descriptive text (test instructions, descriptions) MUST also be written in Chinese:

=== TEST_START ===

[测试框架]
<framework_name or "未检测到">

[测试统计]
测试文件数    : NNN
估计测试数    : NNN

[测试组织]
<description of test layout in Chinese>

[运行测试步骤]
1. <step in Chinese>
2. <step in Chinese>
...

[仿真/基准测试方法]
<description of each method in Chinese, or "此仓库中未检测到仿真或基准测试方法。">

[运行仿真/基准测试步骤]
1. <step in Chinese>
2. <step in Chinese>
...
(or "不适用 - 未检测到仿真或基准测试。")

[CI 配置]
<description of CI setup in Chinese, or "未检测到 CI 配置。">

=== TEST_END ===