behave-retry 1.0.0__tar.gz

behave_retry-1.0.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,44 @@
+---
+name: Bug report
+about: Report a bug or unexpected behavior
+title: "[BUG] "
+labels: bug
+assignees: []
+---
+
+## Describe the bug
+
+A clear and concise description of what the bug is.
+
+## To reproduce
+
+Steps to reproduce the behavior:
+
+1. ...
+2. ...
+3. ...
+
+Minimal code example:
+
+```python
+# Your code here
+```
+
+## Expected behavior
+
+What you expected to happen.
+
+## Actual behavior
+
+What actually happened.
+
+## Environment
+
+- **Python version:**
+- **behave-retry version:**
+- **behave version:**
+- **OS:**
+
+## Additional context
+
+Any other context, logs, or screenshots.

behave_retry-1.0.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest a new feature or enhancement
+title: "[FEATURE] "
+labels: enhancement
+assignees: []
+---
+
+## Problem
+
+A clear description of the problem this feature would solve.
+
+## Proposed solution
+
+A description of what you want to happen.
+
+## Alternatives considered
+
+Any alternative solutions or features you've considered.
+
+## Additional context
+
+Any other context, screenshots, or examples.

behave_retry-1.0.0/.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Description
+
+Brief description of the changes in this PR.
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+- [ ] Refactor (no functional changes)
+- [ ] Test improvement
+
+## Related issues
+
+Closes #
+
+## Checklist
+
+- [ ] My code follows the project style (ruff passes)
+- [ ] I have added tests for my changes
+- [ ] All tests pass (`pytest tests/ -v`)
+- [ ] Coverage stays at or above 90%
+- [ ] I have updated the CHANGELOG.md (if applicable)
+- [ ] I have updated the documentation (if applicable)
+
+## Additional notes
+
+Any extra context for reviewers.

behave_retry-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,59 @@
+name: CI
+
+on:
+  push:
+    tags: ["v*"]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: pytest tests/ -v --cov --cov-report=xml
+      - uses: codecov/codecov-action@v4
+        if: matrix.python-version == '3.12'
+        with:
+          file: ./coverage.xml
+
+  build:
+    needs: test
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    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

behave_retry-1.0.0/.github/workflows/release.yml

@@ -0,0 +1,70 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check .
+      - run: pytest tests/ -v --cov
+
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    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
+
+  release-github:
+    needs: publish
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Create GitHub Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          gh release create "${{ github.ref_name }}" \
+            --title "${{ github.ref_name }}" \
+            --generate-notes \
+            dist/*

behave_retry-1.0.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+.eggs/
+*.egg
+.pytest_cache/
+.coverage
+htmlcov/
+coverage.xml
+.tox/
+.mypy_cache/
+.ruff_cache/

behave_retry-1.0.0/CHANGELOG.md

@@ -0,0 +1,21 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [1.0.0] - 2026-07-13
+
+### Added
+
+- `setup_retry()` — configure retry in `before_all` hook
+- `after_scenario_hook()` — handle retry logic in `after_scenario`
+- `retry_report()` — human-readable retry summary
+- `RetryStats` and `ScenarioRetry` dataclasses for stats tracking
+- `RetryConfig` dataclass for configuration
+- `--retry N` CLI flag support
+- `--retry-tags @tag` CLI flag for tag-filtered retry
+- `--retry-on ExceptionType` CLI flag for exception-filtered retry
+- `@retry:N` tag per scenario for override
+- `@retry:0` tag to disable retry for a scenario
+- `after_retry` hook support for cleanup between retries
+- `RetryExhaustedError` exception
+- Zero required dependencies

behave_retry-1.0.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best for the overall community, not just us as
+  individuals
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+  of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards
+of acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies
+when an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**conduct@mathiaspaulenko.com**.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited
+interaction with those enforcing the Code of Conduct, is allowed during this
+period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla coc]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

behave_retry-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,145 @@
+# Contributing to behave-retry
+
+Thank you for your interest in contributing to behave-retry! This document
+covers everything you need to know to get started.
+
+## Prerequisites
+
+- Python 3.11 or higher
+- [uv](https://github.com/astral-sh/uv) or pip
+- Git
+
+## Getting started
+
+```bash
+git clone https://github.com/MathiasPaulenko/behave-retry.git
+cd behave-retry
+pip install -e ".[dev]"
+```
+
+Verify your setup:
+
+```bash
+ruff check .
+pytest tests/ -v
+```
+
+## Development workflow
+
+### 1. Create a branch
+
+```bash
+git checkout -b feat/my-feature
+```
+
+Use the following prefixes:
+
+- `feat/` — new features
+- `fix/` — bug fixes
+- `docs/` — documentation changes
+- `refactor/` — code refactoring
+- `test/` — test additions or fixes
+- `chore/` — tooling, CI, dependencies
+
+### 2. Make your changes
+
+- Follow the existing code style. Ruff enforces it automatically.
+- Keep functions small and focused (single responsibility).
+- Use type hints on all parameters and return types.
+- Write docstrings in Google or NumPy format.
+- Add or update tests for any changed behavior.
+
+### 3. Run checks locally
+
+```bash
+ruff check .
+pytest tests/ -v --cov
+```
+
+Both must pass before opening a PR. Coverage must stay at or above 90%.
+
+### 4. Commit your changes
+
+Write clear, concise commit messages. Use the imperative mood:
+
+```text
+Add exception filtering to retry config
+Fix off-by-one in retry attempt counter
+Update README with API reference table
+```
+
+### 5. Open a pull request
+
+Push your branch and open a PR against `main`. Fill in the PR template and
+link any related issues.
+
+## Code style
+
+This project uses [Ruff](https://github.com/astral-sh/ruff) with the following
+rule sets: `E`, `F`, `W`, `I`, `N`, `UP`, `B`, `SIM`.
+
+Key conventions:
+
+- Line length: 100 characters
+- Import sorting: `isort`-compatible (first-party: `behave_retry`)
+- Use `from __future__ import annotations` in all modules
+- Prefer dataclasses for structured data
+- No comments that don't add value
+
+## Testing
+
+Tests live in `tests/` and use `pytest`. The project uses fake objects
+(`FakeScenario`, `FakeContext`) to test hooks without a real Behave runner.
+
+```bash
+# Run all tests
+pytest tests/ -v
+
+# Run with coverage
+pytest tests/ -v --cov
+
+# Run a single test file
+pytest tests/test_config.py -v
+```
+
+## Pull request guidelines
+
+- One feature or fix per PR.
+- Include tests for any new behavior.
+- Keep PRs small and focused for easier review.
+- Update the CHANGELOG.md under an `## [Unreleased]` section.
+- Ensure CI passes: `ruff check .` and `pytest tests/ -v --cov`.
+
+## Reporting bugs
+
+Open a [bug report issue](https://github.com/MathiasPaulenko/behave-retry/issues/new?template=bug_report.md)
+and include:
+
+- Python version
+- behave-retry version
+- Minimal reproduction steps
+- Expected vs actual behavior
+
+## Suggesting features
+
+Open a [feature request issue](https://github.com/MathiasPaulenko/behave-retry/issues/new?template=feature_request.md)
+and describe:
+
+- The problem you're trying to solve
+- Your proposed solution
+- Any alternatives you've considered
+
+## Release process
+
+Releases are automated through GitHub Actions:
+
+1. Update `version` in `pyproject.toml` and `__version__` in `__init__.py`.
+2. Update `CHANGELOG.md` with the new version and date.
+3. Tag the commit: `git tag v1.x.x`.
+4. Push the tag: `git push origin v1.x.x`.
+5. CI builds the package and publishes to PyPI via trusted publishing (OIDC).
+
+## Questions?
+
+Open a [discussion](https://github.com/MathiasPaulenko/behave-retry/discussions)
+or an issue. We're happy to help.

behave_retry-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mathias Paulenko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.