Topic: Check for pyproject.toml, pytest.ini, or conftest.py at the repo root to confirm whether testertest*.py files are explicitly excluded from pytest collection.

Date: 2026-05-29

Time: 08:08

No Pytest Configuration Exists — testertest*.py Files Are Not Excluded

The repository has no pytest configuration at all. None of the standard configuration files exist:

| File | Status |

|------|--------|

| pyproject.toml | Not found |

| pytest.ini | Not found |

| setup.cfg | Not found |

| conftest.py (root) | Not found |

Without any of these files, pytest falls back entirely to its default collection rules: it recurses from the invocation directory, collects files matching test*.py and *test.py, and runs functions/classes matching test_*/Test*.

What this means for testertest*.py

Files named testertest*.py would be collected by pytest under default rules, because they match the *test.py glob pattern. There is no collectignore, norecursedirs, testpaths, or python_files setting anywhere in the repo to override this — the grep for these directives across all files returned zero matches.

The .gitignore (4 lines) only excludes _pycache/, *.pyc, and .pytestcache/ — standard cache artifacts, nothing test-related.

Bottom line

If testertest*.py files exist in this repo and someone runs pytest from the root, pytest will discover and attempt to run them. There is no exclusion mechanism in place. If these files are intended as test infrastructure (not test suites themselves), this is a latent problem — they'll be collected and likely fail or produce confusing results.