Dev

.github/workflows/ci.yml

@@ -1,6 +1,3 @@
-# This workflow will install Python dependencies, run tests and lint with a variety of Python versions
-# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
-
 name: CI
 
 on:
@@ -11,27 +8,21 @@ on:
 
 jobs:
   tests:
-
     runs-on: ubuntu-latest
     strategy:
       fail-fast: false
       matrix:
-        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
+        python-version: ["3.10", "3.11", "3.12"]
 
     steps:
     - uses: actions/checkout@v4
     - name: Set up Python ${{ matrix.python-version }}
       uses: actions/setup-python@v4
       with:
         python-version: ${{ matrix.python-version }}
+    - name: Install uv
+      uses: astral-sh/setup-uv@v3
     - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
-    - name: Install tox and any other packages
-      run: |
-        pip install tox
-    - name: Run tox
-      # Run tox using the version of Python in `PATH`
-      run: |
-        tox run -e py$(echo ${{ matrix.python-version }})
+      run: uv sync --frozen
+    - name: Run tests
+      run: uv run pytest -xv tests/

.gitignore

@@ -2,3 +2,6 @@
 __pycache__/
 dist/
 *.egg-info/
+.venv/
+estudo/
+validacao-experimentos/

.pre-commit-config.yaml

@@ -6,20 +6,16 @@ repos:
       - id: end-of-file-fixer
         exclude: '.*\.pth$'
       - id: debug-statements
+  - repo: https://github.com/astral-sh/uv-pre-commit
+    rev: v0.5.0
+    hooks:
+      - id: uv-lock
   - repo: https://github.com/codespell-project/codespell
     rev: v2.2.6
     hooks:
       - id: codespell
-  - repo: https://github.com/PyCQA/isort
-    rev: 5.12.0
-    hooks:
-      - id: isort
-  - repo: https://github.com/asottile/pyupgrade
-    rev: v3.3.1
-    hooks:
-      - id: pyupgrade
-        args: [--py37-plus]
-  - repo: https://github.com/PyCQA/flake8
-    rev: 6.0.0
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.1
     hooks:
-      - id: flake8
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]

CHANGELOG.md

@@ -1,61 +1,124 @@
 
 # Changelog
 
-0.3.3 (2024-04-08)
-----
-
-* Add replay option
-* Refine random order and test group level
-* Code refactoring
-
-0.3.3 (2024-12-24)
-----
-
-* Support order dependency
-
-0.3.2 (2024-12-23)
-----
-
-* Refine test group level definition and extraction
-* Use pytest test discovery order as default
-
-0.3.1 (2024-06-06)
-----
-
-* Support ranking tests at different granularity levels (PUT, method, file, folder)
-* Add plugin summary via pytest_terminal_summary
-
-0.3.0 (2024-05-12)
-----
-
-* Fix attribute initialization in change tracker for Python 3.11 and lower versions
-
-
-0.2.8 (2024-05-08)
-----
-
-* Make pytest-xdist compatible for random and change-related heuristics
-
-
-0.2.7 (2024-03-18)
-----
-
-* Add option to run tests in random order
-* Improve documentation
-
-
-
-
-0.2.0 (2024-02-16)
-----
-
-* Add textual similarity between tests and changed files since last run as the third heuristic
-* Weight normalization
-* History length as an optional argument
-* Rename plugin to `pytest-ranking`
-
-
-0.1.0 (2023-12-04)
-----
-
-* First release on PyPI
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased] pytest-regsmart
+
+## [0.6.3] - 2026-08-29
+
+### Added
+- Hotfix: Resolve base branch to the merge destination instead of current branch
+- Add validation for args options in pytest.ini
+- Add default values for diff-level, rank-level and no-rank flags in pytest.ini
+## [0.6.2] - 2026-08-22
+
+### Added
+- New `--diff-level` flag to choose the diff granularity: `function`pr (default) or `file`
+- Track deleted files in the diff result
+## [0.6.1] - 2026-08-11
+
+### Changed
+- License changed from MIT to GPLv2+
+### Added
+- Default branch information in summary log report
+## [0.6.0] - 2026-08-10
+
+### Security
+- Bump pytest from version 7.4.3 to 9.0.3 ([CVE-2025-71176](https://github.com/leticosta4/pytest-regsmart/security/dependabot/1))
+- Bump gitpython from 3.1.57 to 3.1.58 ([CVEs](https://github.com/leticosta4/pytest-regsmart/security/dependabot?q=GitPython+is%3Aclosed))
+### Removed
+- Support for Python 3.8 and 3.9
+## [0.5.0] - 2026-08-07
+
+### Added
+- Regression Test Selection (RTS): a new `selection` module that computes the test files affected by the current changes and runs only them under `--regsmart`
+  - Detect changed files with git (modified + untracked) against the resolved default branch (origin/HEAD → main/master → active branch); repositories without commits fall back to untracked files only
+  - Build a module-level dependency graph with pyan3 and propagate changes transitively (BFS) to affected test files
+  - Raise a `UsageError` when `--regsmart` is used outside a git repository
+- Report the RTS configuration and timing in the terminal header/summary
+- Integration tests for the selection module and improved test suite
+### Changed
+- Refine `--no-rank`: it now only disables RTP while keeping RTS active, and cannot be combined with other `--rank-*` flags (raises a `UsageError`)
+## [0.4.0] - 2026-07-24
+
+### Added
+- `--no-rank` option to remove RTP, considering only the future RTS module
+### Changed
+- Rename activation flag from `--rank` to `--regsmart`
+- Improve documentation
+## [0.3.0] - 2026-07-20
+
+### Changed
+- Migrate package manager to uv
+## [0.2.0] - 2026-07-19
+
+### Changed
+- Rename whole package name to `pytest-regsmart`
+- Refactor ranking module internals (modularization)
+### Removed
+- Directory-level granularity (`--rank-level=dir`)
+## [0.1.0] - 2026-06-25
+
+### Added
+- Fork of pytest-ranking (based on PyPI release 0.3.4)
+### Changed
+- Rename plugin to `pytest-regsmart`
+### Removed
+- Similar Changed Path method (`--rank-weight=0-0-1`)
+
+---
+
+## Inherited history (pytest-ranking)
+
+## [0.3.4] - 2025-04-09
+
+### Added
+- Replay option
+- Published version at [PyPI](https://pypi.org/project/pytest-ranking/0.3.4/#history)
+### Changed
+- Refine random order and test group level
+- Code refactoring
+## [0.3.3] - 2024-12-24
+
+### Added
+- Support order dependency
+## [0.3.2] - 2024-12-23
+
+### Changed
+- Refine test group level definition and extraction
+- Use pytest test discovery order as default
+## [0.3.1] - 2024-06-06
+
+### Added
+- Support ranking tests at different granularity levels (PUT, method, file, folder)
+- Plugin summary via `pytest_terminal_summary`
+## [0.3.0] - 2024-05-12
+
+### Fixed
+- Attribute initialization in change tracker for Python 3.11 and lower versions
+## [0.2.8] - 2024-05-08
+
+### Fixed
+- pytest-xdist compatibility for random and change-related heuristics
+## [0.2.7] - 2024-03-18
+
+### Added
+- Option to run tests in random order
+### Changed
+- Improve documentation
+## [0.2.0] - 2024-02-16
+
+### Added
+- Textual similarity between tests and changed files since last run as the third heuristic
+- History length as an optional argument
+### Changed
+- Weight normalization
+- Rename plugin to `pytest-ranking`
+## [0.1.0] - 2023-12-04
+
+### Added
+- First release on PyPI

docs/DEPLOYMENT.md → DEPLOYMENT.md

@@ -1,51 +1,63 @@
 # Deployment
 
-## Using pytest-ranking in fixed location
+## Using pytest-regsmart in fixed location
 
-If your CI runs different test builds in a fixed location, e.g., a project folder in specific machine, you can directly use `pytest-ranking` after installation without additional setup.
+If your CI runs different test builds in a fixed location, e.g., a project folder in specific machine, you can directly use `pytest-regsmart` after installation without additional setup.
 
-## Using pytest-ranking in Github Actions
+## Using pytest-regsmart in Github Actions
 
 If your CI workflow always starts a new virtual machine to run a test build, you need to set up the CI to be able to pass `pytest` cache data across test builds.
 Here, we use GitHub Actions as an example.
 
-### Add pytest-ranking to project dependency
+### Check out the full history
 
+`pytest-regsmart` computes the diff against the **base** (destination) branch — e.g. `main` for a PR or push. GitHub Actions' default checkout does a shallow, single-branch clone (`fetch-depth: 1`), which does not fetch that base branch, so the base cannot be resolved and `pytest-regsmart` raises a `UsageError`. Fetch the full history:
 
-You can add `pytest-ranking` as a dependency by adding a installation job before the job that runs `pytest ...` (a job is often specified by `-name: `) in the workflow file:
+```yml
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+```
+
+This only affects the clone metadata, not the working-tree files, so the added time is negligible even for large repositories.
+
+### Add pytest-regsmart to project dependency
+
+
+You can add `pytest-regsmart` as a dependency by adding a installation job before the job that runs `pytest ...` (a job is often specified by `-name: `) in the workflow file:
 
 ```yml
-    - name: Install pytest-ranking related
-      run: pip install pytest-ranking
+    - name: Install pytest-regsmart related
+      run: pip install pytest-regsmart
 ```
 
-Alternatively, depending on where the forked project puts its dependency, e.g., can be in `setup.py`, `pyproejct.toml`, you can also add the `pytest-ranking` to the build/test dependency, but best not to specify version.
+Alternatively, depending on where the forked project puts its dependency, e.g., can be in `setup.py`, `pyproejct.toml`, you can also add the `pytest-regsmart` to the build/test dependency, but best not to specify version.
 
 
 #### If the project uses `Tox`
 
-Add `pytest-ranking` to the `deps` of `[testenv]` in `./tox.ini`:
+Add `pytest-regsmart` to the `deps` of `[testenv]` in `./tox.ini`:
 ```ini
 [testenv]
 deps =
   ; ...
-  pytest-ranking
+  pytest-regsmart
   pytest-json-report
 ```
 
 
 ### Setup pytest_cache
 
-Before the job in the workflow file that runs the `pytest ...` but after the `pytest-ranking` installation job, add the job that restores cache from the latest run if such run exists:
+Before the job in the workflow file that runs the `pytest ...` but after the `pytest-regsmart` installation job, add the job that restores cache from the latest run if such run exists:
 
 ```yml
-    - name: Restore pytest-ranking cache
-      id: restore-pytest-ranking-cache
+    - name: Restore pytest-regsmart cache
+      id: restore-pytest-regsmart-cache
       if: always()
       uses: actions/cache/restore@v4
       with:
         path: ${{ github.workspace }}/.pytest_cache/v/pytest_ranking_data
-        key: pytest-ranking-cache-${{ github.workflow }}-${{ runner.os }}-${{ matrix.python }}
+        key: pytest-regsmart-cache-${{ github.workflow }}-${{ runner.os }}-${{ matrix.python }}
     # --------below is the job for running pytest
     -name: pytest
         ...
@@ -57,13 +69,13 @@ And after the job that runs `pytest ...` command, add the job that caches result
     -name: pytest
         ...
     # --------above is the job for running pytest
-    - name: Save pytest-ranking cache
-      id: save-pytest-ranking-cache
+    - name: Save pytest-regsmart cache
+      id: save-pytest-regsmart-cache
       if: always()
       uses: actions/cache/save@v4
       with:
         path: ${{ github.workspace }}/.pytest_cache/v/pytest_ranking_data
-        key: pytest-ranking-cache-${{ github.workflow }}-${{ runner.os }}-${{ matrix.python }}-${{ github.run_id }}
+        key: pytest-regsmart-cache-${{ github.workflow }}-${{ runner.os }}-${{ matrix.python }}-${{ github.run_id }}
 ```
 
 #### If the project uses `Tox`