pytest-filemon 0.1.0__tar.gz

pytest_filemon-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  dogfood:
+    # The plugin's own suite through the plugin itself: the first run
+    # records, the no-change rerun must select nothing (and exit 0).
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+
+      - name: Install
+        run: uv sync
+
+      - name: Run tests (filemon dogfood)
+        run: |
+          uv run pytest --filemon -q tests   # records: everything runs
+          uv run pytest --filemon -q tests   # nothing changed: 0 selected, exit 0
+
+  tests:
+    # The plain suite on every supported Python.
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ["3.9", "3.10", "3.11", "3.12", "3.13", "3.14", "3.15"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --python ${{ matrix.python }}
+      - run: uv run --python ${{ matrix.python }} pytest -q tests
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync
+      - run: uv run ruff check src tests

pytest_filemon-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,65 @@
+name: publish
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: Where to publish
+        required: true
+        default: testpypi
+        type: choice
+        options:
+          - testpypi
+          - pypi
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+
+      - run: uv sync
+      - run: uv run pytest -q tests
+      - run: uv build
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+  publish-testpypi:
+    needs: build
+    if: github.event_name == 'workflow_dispatch' && inputs.target == 'testpypi'
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  publish-pypi:
+    needs: build
+    if: github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && inputs.target == 'pypi')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

pytest_filemon-0.1.0/.gitignore

@@ -0,0 +1,8 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+dist/
+build/
+.pytest_cache/
+.pytest_filemon/

pytest_filemon-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

pytest_filemon-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 pytest-filemon developers
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

pytest_filemon-0.1.0/PKG-INFO

@@ -0,0 +1,206 @@
+Metadata-Version: 2.5
+Name: pytest-filemon
+Version: 0.1.0
+Summary: File-level test impact analysis for pytest: per-test import dependencies recorded by wrapping __import__ (cached imports included), stored as local JSON, selected by file fingerprints.
+Project-URL: Homepage, https://github.com/gnufede/pytest-filemon
+Project-URL: Repository, https://github.com/gnufede/pytest-filemon
+Project-URL: Issues, https://github.com/gnufede/pytest-filemon/issues
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: Pytest
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.9
+Requires-Dist: pytest>=7.4
+Description-Content-Type: text/markdown
+
+# pytest-filemon
+
+**File-level test impact analysis (TIA)** for pytest — Filemón, the file-level
+partner of [pytest-mortadelo](https://github.com/gnufede/pytest-mortadelo)
+(block-level).  Both work for the T.I.A. — here: Test Impact Analysis.
+
+| | pytest-filemon |
+|---|---|
+| dependency storage | local JSON under `.pytest_filemon/` (not versioned; copy the directory to share it) |
+| dependency unit | **whole files**: any change to a dependency file re-runs its dependents |
+| dependency collection | wraps `builtins.__import__` and `importlib.import_module` — **every import statement, cached imports included**; no code instrumentation |
+| import-time dependencies | everything imported before tests start is a dependency of *every* test; modules imported before arming are claimed, and their ASTs backfilled as possible dependencies |
+| change detection | **file fingerprints** (size, mtime, content hash) — git only for new-file questions; `git diff` is the fallback |
+| Python support | **3.9+** — no `sys.monitoring`, no bytecode analysis; anything that runs pytest |
+
+Requires a git repository.
+
+## Usage
+
+```bash
+pip install pytest-filemon
+
+pytest --filemon              # first run: everything runs, dependencies are recorded
+pytest --filemon              # second run: only tests whose dependency files changed
+```
+
+Options:
+
+| option | effect |
+|---|---|
+| `--filemon` | enable recording + selection |
+| `--filemon-force` | run all tests, but still record dependencies |
+| `--filemon-clean` | discard the stored data before running |
+| `PYTEST_FILEMON=1` | same as `--filemon` (env form; also enables before conftest loading) |
+| `-p no:filemon` | disable the plugin entirely |
+
+If nothing changed and nothing failed, **zero tests run and pytest exits
+with code 0**: deselecting everything is a successful selection, not an
+error.  (A genuinely empty collection keeps pytest's own exit code 5.)
+
+## How it works
+
+### The import wraps
+
+The recorder wraps `builtins.__import__` — the single choke point every
+`import` and `from ... import ...` statement runs through, **hit or miss**
+— and `importlib.import_module`.  Each executed statement is resolved to
+the repository files it names (the imported module, and its parent
+packages, which execute at import too) and recorded as a dependency of
+whatever is running:
+
+- **import phase** (before collection: pytest plugins, conftest imports)
+  → dependencies of *every* test.  Modules already imported at arming
+  time have no statements left to see, so they are claimed from
+  `sys.modules`, and their full ASTs are backfilled: every import
+  statement in them — including dead branches — whose target is present
+  in `sys.modules` becomes a dependency.  Backfill deliberately
+  over-approximates what ran before the recorder existed.
+- **collect phase** (test module imports) → a test module's own imports
+  belong to its tests; a test module imported by pytest's machinery is a
+  dependency of its own tests; everything else is shared by every test.
+- **test phase** → attributed to the running test's node id.
+
+The wraps see **cached** imports — an import that hits `sys.modules`
+fires no code event anywhere, but the statement still runs through
+`__import__`, which is what makes whole-file dependencies complete
+without any instrumentation: to call into a module, a test must execute
+an import statement for it.  This is also why filemon needs none of
+mortadelo's extra machinery (the bytecode import scan, the fixture
+closure, the `lru_cache` wrap): at file granularity, the plain import
+edges subsume all three.
+
+**Subprocess boundaries (always on):** the functions that create
+processes are wrapped (`subprocess.Popen`, `os.system`,
+`os.fork`/`posix_spawn`/`exec*`, `_posixsubprocess.fork_exec` — which
+also covers `multiprocessing`).  Coverage cannot follow a child
+process, so when a test spawns one the recorder **stops collecting for
+that test, writes no dependencies for it, and lists it in the data's
+`always` key: it re-runs whenever anything changed** (reported as `N
+always re-run (spawn subprocesses)`); a rerun with *provably nothing
+changed* skips them like everything else via the no-change fast path.
+
+The active configuration file (`pytest.ini` / `pyproject.toml` / ...)
+is claimed as a shared dependency: a config change selects everything.
+
+### Storage and selection
+
+```
+.pytest_filemon/
+├── data.json   {"version":1, "files":[...], "tests":{nodeid:[file-index...]}, "import_deps":[...], "failed":[...], "always":[...]}
+├── meta.json   {"version":1, "base_commit":..., "created":..., "failed":[...], "nodeids":[...], "dep_files":[...]}
+└── files.json  {"v":1, "at":ns, "files":{file:[size, mtime_ns, hash]}, "dirs":{dir:[subdirs]}}
+```
+
+One dataset for the whole repository; each file replaced atomically.  The
+change detection (fingerprints: stat first, hash on doubt, racy-mtime
+protection, new-file detection through one scoped `git ls-files`) is
+shared code with pytest-mortadelo — see its README for the details.
+
+A test runs when it has no recorded data (new), failed in the recorded
+run, one of its dependency files is in `changed`, a shared import-time
+dependency changed, or it is a spawner and anything changed.  Selectors
+(`-k`, `-m`, `--lf`, explicit `file.py::test` arguments) disable
+selection entirely: an explicitly requested but unaffected test must
+never be silently skipped.
+
+## File granularity, honestly
+
+Filemon re-runs *every* dependent of a changed file, even for a one-line
+edit in a branch the test never touched — that is the trade: no
+instrumentation, any Python, tiny overhead.  What it does **not** see:
+
+- **Stored / dynamic code paths**: a test only depends on files it (or
+  its module at collection, or a conftest in its chain) *imports*.  A
+  test that calls `stored_functions[0]()` — a function defined in
+  `lib.py` and appended to a list at import time — records a dependency
+  on `lib.py` only if that import happened in its own chain.  When the
+  list was filled by *another test module's* import, the edge belongs to
+  that module's tests alone and this test records nothing: edit
+  `lib.py`, and this test is silently skipped.
+- **`.so` artifacts are files too**: `import fast` resolves the
+  extension module's path — a rebuild re-runs its importers.  `ctypes`
+  dlopen without an import statement is not seen (mortadelo's world had
+  the same limit).
+- **Data files** (fixtures, configs beyond the active pytest ini): not
+  dependencies — nothing executes them.
+- **Backfill is an over-approximation**: before the recorder armed,
+  imports in dead branches of already-loaded modules count as
+  dependencies once their target is in `sys.modules`.  Post-arm events
+  record only executed statements.
+- **State-dispatched tests** (env vars, the clock, randomness): the
+  fundamental limit of any TIA.
+
+For block-level precision (function/class granularity, stale-block
+intersection, module skeletons), use
+[pytest-mortadelo](https://github.com/gnufede/pytest-mortadelo).
+
+## Development
+
+The repo is managed with [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv sync            # create/update .venv from uv.lock (dev tools included)
+uv run pytest      # run the test suite (syncs automatically if needed)
+uv run ruff check src tests
+```
+
+The test suite uses `pytester` subprocess runs against real git
+repositories, so it needs network-free local git only.
+
+### Live demo
+
+`demo/sqlalchemy_demo.py` runs a live overhead + edit→deselect benchmark
+against sqlalchemy's ORM suite (2,480 tests over 12 files), with only
+comment or no-op edits — nothing breaks, everything is restored:
+
+```bash
+python3 demo/sqlalchemy_demo.py [path-to-sqlalchemy-checkout]
+```
+
+If the checkout has no `.venv*` virtualenv, the demo creates
+`<checkout>/.venv` and installs sqlalchemy, pytest and this plugin
+editable into it. Set `SQLALCHEMY_PYTHON` to use an existing interpreter.
+
+Pytest output is streamed live, each edit is shown as a colored
+`git diff`, and the demo waits for Enter between steps, so it can be
+driven as a live walkthrough.
+
+It shows the record overhead, the no-change fast path (0 tests, exit 0,
+under a second), and where the deselect boundary sits — see the script
+header for details.
+
+## Layout
+
+```
+src/pytest_filemon/
+├── plugin.py      # pytest hooks, lifecycle, options
+├── imports.py     # the import wraps: __import__ / import_module + backfill
+├── fingerprint.py # [size, mtime_ns, hash] snapshots and change detection
+├── selection.py   # stored-data parsing + test selection
+├── store.py       # .pytest_filemon/ JSON storage
+└── util.py        # path normalization
+```