pytest-shard-cloudc 0.1.2__tar.gz

pytest_shard_cloudc-0.1.2/.circleci/config.yml

@@ -0,0 +1,17 @@
+version: 2.1
+
+executors:
+  my-executor:
+    docker:
+      - image: cimg/python:3.11
+    environment:
+      NUM_CPUS: 2  # more CPUs visible but we're throttled to 2, which breaks auto-detection of parallelism
+
+jobs:
+  build:
+    executor: my-executor
+
+    steps:
+      - checkout
+      - run: python -m pip install -e .[dev]
+      - run: nox --no-venv -s tests -s shard-0 -s shard-1 -s lint -s typing

pytest_shard_cloudc-0.1.2/.github/workflows/ci.yml

@@ -0,0 +1,28 @@
+name: CI
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: pip install -e ".[dev]"
+
+      - name: Run tests and lint
+        run: nox --no-venv -s tests -s shard-0 -s shard-1 -s lint -s typing

pytest_shard_cloudc-0.1.2/.github/workflows/publish-testpypi.yml

@@ -0,0 +1,50 @@
+name: Publish to TestPyPI
+
+on:
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade build
+
+      - name: Build wheel and sdist
+        run: |
+          python -m build
+
+      - name: Upload dist artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish:
+    name: Publish to TestPyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download dist artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/

pytest_shard_cloudc-0.1.2/.github/workflows/publish.yml

@@ -0,0 +1,50 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install build tools
+        run: |
+          python -m pip install --upgrade build
+
+      - name: Build wheel and sdist
+        run: |
+          python -m build
+
+      - name: Upload dist artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for Trusted Publishing (OIDC)
+
+    steps:
+      - name: Download dist artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

pytest_shard_cloudc-0.1.2/.gitignore

@@ -0,0 +1,140 @@
+# Local development artifacts
+REFACTOR_PLAN.md
+logs/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# PyCharm project settings
+.idea/
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# pytype
+.pytype/
+
+# Pyre type checker
+.pyre/
+
+# Allure
+allure-results/
+allure-report/
+allure-report-*/

pytest_shard_cloudc-0.1.2/LICENSE

@@ -0,0 +1,8 @@
+Copyright 2019 Adam Gleave
+Copyright 2026 Cloud Chen
+
+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.

pytest_shard_cloudc-0.1.2/PKG-INFO

@@ -0,0 +1,162 @@
+Metadata-Version: 2.4
+Name: pytest-shard-cloudc
+Version: 0.1.2
+Summary: Shard tests to support parallelism across multiple machines.
+Project-URL: Homepage, https://github.com/wolke1007/pytest-shard-cloudc
+Project-URL: Repository, https://github.com/wolke1007/pytest-shard-cloudc
+Project-URL: Original Project, https://github.com/AdamGleave/pytest-shard
+Author-email: Cloud Chen <wolke1007@users.noreply.github.com>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ci,distributed,parallel,pytest,shard,testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.11
+Requires-Dist: pytest
+Provides-Extra: dev
+Requires-Dist: allure-pytest; extra == 'dev'
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: hypothesis; extra == 'dev'
+Requires-Dist: mypy; extra == 'dev'
+Requires-Dist: nox; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Description-Content-Type: text/markdown
+
+[![PyPI version](https://badge.fury.io/py/pytest-shard-cloudc.svg)](https://badge.fury.io/py/pytest-shard-cloudc)
+
+[繁體中文](README.zh-TW.md) | **English**
+
+# pytest-shard
+
+> **This is a fork of [AdamGleave/pytest-shard](https://github.com/AdamGleave/pytest-shard) by [Cloud Chen](https://github.com/wolke1007).**
+> Modifications include: Allure report integration, multi-shard result merging, nox-based tooling, and modernized packaging with `pyproject.toml`.
+
+`pytest-shard` splits your test suite across multiple machines or CI workers at individual test-case granularity. By default it sorts tests by node ID and assigns them round-robin across shards, so parallelism works even when all tests live in a single file or a single parameterized method.
+
+## How It Works
+
+See [Sharding Modes](doc/sharding-modes.md) for separate diagrams that explain how `roundrobin`, `hash`, and `duration` assign tests to shards.
+
+## What it does
+
+| Capability | Description |
+|------------|-------------|
+| **Round-robin sharding** (default) | Sorts tests by node ID and interleaves across shards, guaranteeing shard counts differ by at most 1 |
+| **Hash-based sharding** | Assigns each test deterministically via `SHA-256(node_id) % N` — per-test stable even as the suite grows |
+| **Duration-based sharding** | Greedy bin-packing using a `.test_durations` file (compatible with pytest-split) to minimise the longest shard |
+| **Zero configuration** | Just add `--shard-id` and `--num-shards` — no config files, no test ordering required |
+| **Any granularity** | Splits at the individual test level, not at the file or class level |
+| **CI-agnostic** | Works with GitHub Actions, CircleCI, Travis CI, or any system that runs parallel jobs |
+| **Allure integration** | Collect results per shard, merge them, and view a unified Timeline report |
+
+## Documentation
+
+| Guide | Description |
+|-------|-------------|
+| [Sharding Modes](doc/sharding-modes.md) | Detailed behavior of `roundrobin`, `hash`, and `duration`, including `.test_durations`, verbose shard reports, and mode selection guidance. |
+| [Demo Sessions](doc/demo-sessions.md) | How contributors can run the bundled demo suites locally with `nox`. |
+| [Allure Report Integration](doc/allure-integration.md) | How to collect Allure results across shards, merge them into one report, run shards in parallel locally, and integrate with GitHub Actions / CircleCI. Includes a worked example with 30 tests across 3 parallel shards and a Timeline screenshot. |
+
+## Quick start
+
+### Installation
+
+```bash
+pip install pytest-shard-cloudc
+```
+
+### Split tests across N machines
+
+```bash
+# Machine 0
+pytest --shard-id=0 --num-shards=3
+
+# Machine 1
+pytest --shard-id=1 --num-shards=3
+
+# Machine 2
+pytest --shard-id=2 --num-shards=3
+```
+
+Each machine runs roughly 1/N of the test suite. Together they cover 100% of tests.
+
+### Choose a sharding mode
+
+```bash
+# Round-robin (default) — guaranteed count balance
+pytest --shard-id=0 --num-shards=3 --shard-mode=roundrobin
+
+# Hash — per-test stable assignment, stateless
+pytest --shard-id=0 --num-shards=3 --shard-mode=hash
+
+# Duration — bin-packing by recorded test times, minimises longest shard
+pytest --shard-id=0 --num-shards=3 --shard-mode=duration --durations-path=.test_durations
+```
+
+See [Sharding Modes](doc/sharding-modes.md) for detailed trade-offs, `.test_durations` generation, and mode selection guidance.
+
+### GitHub Actions example
+
+```yaml
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        shard_id: [0, 1, 2]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install pytest-shard-cloudc
+      - run: pytest --shard-id=${{ matrix.shard_id }} --num-shards=3
+```
+
+### CircleCI example
+
+```yaml
+jobs:
+  test:
+    parallelism: 3
+    steps:
+      - run: pytest --shard-id=${CIRCLE_NODE_INDEX} --num-shards=${CIRCLE_NODE_TOTAL}
+```
+
+## More guides
+
+- For mode behavior, `.test_durations`, verbose shard reports, and selection strategy, see [Sharding Modes](doc/sharding-modes.md).
+- For contributor-facing demo commands, see [Demo Sessions](doc/demo-sessions.md).
+- For report generation and parallel execution screenshots, see [Allure Report Integration](doc/allure-integration.md).
+
+## Alternatives
+
+[pytest-xdist](https://github.com/pytest-dev/pytest-xdist) parallelizes tests across CPU cores on a single machine and supports remote workers. A common pattern is to combine both: use `pytest-shard` to split work across CI nodes, and `pytest-xdist` to parallelize within each node.
+
+[pytest-circleci-parallelized](https://github.com/ryanwilsonperkin/pytest-circleci-parallelized) splits by test run time rather than test count, but only at class granularity and only for CircleCI.
+
+## Contributions
+
+Contributions are welcome. The package requires Python 3.11 or newer. Install the development toolchain and run the full check suite:
+
+```bash
+pip install -e .[dev]
+nox
+```
+
+The Allure integration test also requires the `allure` CLI to be available on `PATH`.
+
+## License
+
+MIT licensed.
+
+Original work Copyright 2019 Adam Gleave.
+Modifications Copyright 2026 Cloud Chen.

pytest_shard_cloudc-0.1.2/README.md

@@ -0,0 +1,129 @@
+[![PyPI version](https://badge.fury.io/py/pytest-shard-cloudc.svg)](https://badge.fury.io/py/pytest-shard-cloudc)
+
+[繁體中文](README.zh-TW.md) | **English**
+
+# pytest-shard
+
+> **This is a fork of [AdamGleave/pytest-shard](https://github.com/AdamGleave/pytest-shard) by [Cloud Chen](https://github.com/wolke1007).**
+> Modifications include: Allure report integration, multi-shard result merging, nox-based tooling, and modernized packaging with `pyproject.toml`.
+
+`pytest-shard` splits your test suite across multiple machines or CI workers at individual test-case granularity. By default it sorts tests by node ID and assigns them round-robin across shards, so parallelism works even when all tests live in a single file or a single parameterized method.
+
+## How It Works
+
+See [Sharding Modes](doc/sharding-modes.md) for separate diagrams that explain how `roundrobin`, `hash`, and `duration` assign tests to shards.
+
+## What it does
+
+| Capability | Description |
+|------------|-------------|
+| **Round-robin sharding** (default) | Sorts tests by node ID and interleaves across shards, guaranteeing shard counts differ by at most 1 |
+| **Hash-based sharding** | Assigns each test deterministically via `SHA-256(node_id) % N` — per-test stable even as the suite grows |
+| **Duration-based sharding** | Greedy bin-packing using a `.test_durations` file (compatible with pytest-split) to minimise the longest shard |
+| **Zero configuration** | Just add `--shard-id` and `--num-shards` — no config files, no test ordering required |
+| **Any granularity** | Splits at the individual test level, not at the file or class level |
+| **CI-agnostic** | Works with GitHub Actions, CircleCI, Travis CI, or any system that runs parallel jobs |
+| **Allure integration** | Collect results per shard, merge them, and view a unified Timeline report |
+
+## Documentation
+
+| Guide | Description |
+|-------|-------------|
+| [Sharding Modes](doc/sharding-modes.md) | Detailed behavior of `roundrobin`, `hash`, and `duration`, including `.test_durations`, verbose shard reports, and mode selection guidance. |
+| [Demo Sessions](doc/demo-sessions.md) | How contributors can run the bundled demo suites locally with `nox`. |
+| [Allure Report Integration](doc/allure-integration.md) | How to collect Allure results across shards, merge them into one report, run shards in parallel locally, and integrate with GitHub Actions / CircleCI. Includes a worked example with 30 tests across 3 parallel shards and a Timeline screenshot. |
+
+## Quick start
+
+### Installation
+
+```bash
+pip install pytest-shard-cloudc
+```
+
+### Split tests across N machines
+
+```bash
+# Machine 0
+pytest --shard-id=0 --num-shards=3
+
+# Machine 1
+pytest --shard-id=1 --num-shards=3
+
+# Machine 2
+pytest --shard-id=2 --num-shards=3
+```
+
+Each machine runs roughly 1/N of the test suite. Together they cover 100% of tests.
+
+### Choose a sharding mode
+
+```bash
+# Round-robin (default) — guaranteed count balance
+pytest --shard-id=0 --num-shards=3 --shard-mode=roundrobin
+
+# Hash — per-test stable assignment, stateless
+pytest --shard-id=0 --num-shards=3 --shard-mode=hash
+
+# Duration — bin-packing by recorded test times, minimises longest shard
+pytest --shard-id=0 --num-shards=3 --shard-mode=duration --durations-path=.test_durations
+```
+
+See [Sharding Modes](doc/sharding-modes.md) for detailed trade-offs, `.test_durations` generation, and mode selection guidance.
+
+### GitHub Actions example
+
+```yaml
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        shard_id: [0, 1, 2]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install pytest-shard-cloudc
+      - run: pytest --shard-id=${{ matrix.shard_id }} --num-shards=3
+```
+
+### CircleCI example
+
+```yaml
+jobs:
+  test:
+    parallelism: 3
+    steps:
+      - run: pytest --shard-id=${CIRCLE_NODE_INDEX} --num-shards=${CIRCLE_NODE_TOTAL}
+```
+
+## More guides
+
+- For mode behavior, `.test_durations`, verbose shard reports, and selection strategy, see [Sharding Modes](doc/sharding-modes.md).
+- For contributor-facing demo commands, see [Demo Sessions](doc/demo-sessions.md).
+- For report generation and parallel execution screenshots, see [Allure Report Integration](doc/allure-integration.md).
+
+## Alternatives
+
+[pytest-xdist](https://github.com/pytest-dev/pytest-xdist) parallelizes tests across CPU cores on a single machine and supports remote workers. A common pattern is to combine both: use `pytest-shard` to split work across CI nodes, and `pytest-xdist` to parallelize within each node.
+
+[pytest-circleci-parallelized](https://github.com/ryanwilsonperkin/pytest-circleci-parallelized) splits by test run time rather than test count, but only at class granularity and only for CircleCI.
+
+## Contributions
+
+Contributions are welcome. The package requires Python 3.11 or newer. Install the development toolchain and run the full check suite:
+
+```bash
+pip install -e .[dev]
+nox
+```
+
+The Allure integration test also requires the `allure` CLI to be available on `PATH`.
+
+## License
+
+MIT licensed.
+
+Original work Copyright 2019 Adam Gleave.
+Modifications Copyright 2026 Cloud Chen.