Topic: Check whether any conftest.py files exist in subdirectories that might locally configure collection, even though the root has none

Date: 2026-05-29

Time: 11:39

No conftest.py Files Exist Anywhere in the Repository

The observations conclusively show that zero conftest.py files exist — not at the repo root, and not in any subdirectory.

Evidence

1. Root check (checkrootconftest): Returned "File not found: conftest.py" — no root-level conftest.

2. Full grep (findconftestfiles): Searched the entire codebase for the string conftest. All 11 matches are in .code-expert/topics.json — the topic queue that *tracks this very question*. No actual conftest.py files surfaced.

3. Directory listing (listallconftest): The 147 entries across all module directories show a consistent per-module structure: an implementation file, a test*.py file, and sometimes a testertest_*.py file. No conftest.py appears in any subdirectory.

4. No pytest configuration at all (findpytestiniorconfig, checktestcollectionconfig): No pyproject.toml, pytest.ini, setup.cfg, or tox.ini exists. No collectignore, norecursedirs, or testpaths directives are configured anywhere.

What This Means

Each module directory (e.g., bloom-filter/, raft-consensus/) operates as a fully self-contained unit with no shared test fixtures, no inherited configuration, and no pytest collection customization. When you run pytest from any module directory, it uses pure default discovery rules (test*.py files, Test* classes, test* functions) with no local overrides.

This also means there is no mechanism to:

• Share fixtures across modules (e.g., a common temp-directory fixture)
• Exclude the testertest*.py files from pytest collection via conftest
• Register custom markers or plugins at any level

The testertest*.py files will be collected by pytest's default rules (they match test*.py glob after the tester prefix — actually, they match *test*.py which is not a default pattern, but the files contain test_ prefixed functions that would be collected if pytest enters the file). The lack of any conftest or config to exclude them is architecturally significant.