core-tests 2.0.4__tar.gz → 2.1.0__tar.gz

{core_tests-2.0.4 → core_tests-2.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: core-tests
-Version: 2.0.4
+Version: 2.1.0
 Summary: It contains common elements for testing purposes...
 Author-email: Alejandro Cora González <alek.cora.glez@gmail.com>
 Maintainer: Alejandro Cora González
@@ -22,26 +22,33 @@ 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 :: Implementation :: PyPy
 Requires-Python: >=3.9
 Description-Content-Type: text/x-rst
 License-File: LICENSE
 Requires-Dist: click>=8.1.8
 Requires-Dist: coverage>=7.7.1
 Requires-Dist: environs>=14.1.1
-Requires-Dist: pytest>=7.4.0
-Requires-Dist: pytest-xdist>=3.5.0
 Provides-Extra: dev
-Requires-Dist: core-dev-tools>=1.0.1; extra == "dev"
+Requires-Dist: core-dev-tools>=2.0.0; extra == "dev"
 Dynamic: license-file
 
 core-tests
 ===============================================================================
 
-This project contains basic elements for testing purposes and the ability 
-to run (via console commands) tests and code coverage (unittest-based). This way, we can 
-stick to the `DRY -- Don't Repeat Yourself` principle and avoid code duplication
-in each python project where tests coverage and tests execution are
-expected...
+A reusable library that provides CLI commands for running ``unittest``-based
+tests and generating code coverage reports. It wraps Python's built-in
+``unittest`` framework and ``coverage`` into a ``Click`` command group so
+consuming projects can use ``python manager.py run-tests`` and
+``python manager.py run-coverage`` without duplicating that logic across
+every project in the ecosystem.
+
+This library is intentionally scoped to ``unittest`` and ``coverage``.
+If your project requires ``pytest``-specific features (fixtures, parametrize,
+plugins, parallel execution), install ``pytest`` directly or via
+``core-dev-tools`` and invoke it standalone — it is a better fit for that use
+case than routing it through this abstraction layer.
 
 ===============================================================================
 
@@ -76,32 +83,35 @@ Install from PyPI using pip:
 .. code-block:: bash
 
     pip install core-tests
-
-Or using uv:
-
-.. code-block:: bash
-
-    uv pip install core-tests
+    uv pip install core-tests  # Or using UV...
 
 
 Features
 ===============================================================================
 
-* **Dual Test Engine Support**: Run tests using either `unittest` or `pytest` frameworks
-* **Flexible Test Discovery**: Supports multiple file patterns:
-    - `test_*.py` (standard pattern)
-    - `*_test.py` (alternative pattern)
-    - `tests_*.py` (custom pattern)
-* **Custom Pattern Support**: Specify custom file patterns using the `--pattern` flag
-* **Test Organization**: Run tests by type (unit, integration, functional, etc.)
-* **Coverage Reports**: Generate coverage reports with both frameworks
-* **CLI Integration**: Easy integration via Click command collections
+* **Unified CLI abstraction**: Expose ``run-tests`` and ``run-coverage`` in any
+  project without duplicating boilerplate — just wire ``cli_tests`` into your
+  ``CommandCollection``.
+* **Flexible Test Discovery**: Supports multiple file patterns out of the box:
+
+    - ``test_*.py`` (standard pattern)
+    - ``*_test.py`` (alternative pattern)
+    - ``tests_*.py`` (custom pattern)
+
+* **Custom Pattern Support**: Override discovery with ``--pattern`` for
+  non-standard file layouts.
+* **Test Organization**: Target specific test directories (unit, integration,
+  functional, etc.) via ``--test-type``.
+* **Branch Coverage Reports**: Generate branch-level coverage reports and
+  optional HTML output.
+* **DRY principle**: One implementation shared across all projects in the
+  ecosystem.
 
 
 How to Use
 ===============================================================================
 
-Create a ``manager.py`` file in your project root to integrate 
+Create a ``manager.py`` file in your project root to integrate
 the test commands:
 
 .. code-block:: python
@@ -116,7 +126,7 @@ the test commands:
 
 This setup provides two commands:
 
-* ``run-tests``: Execute test suites with unittest or pytest
+* ``run-tests``: Execute unittest-based test suites
 * ``run-coverage``: Generate code coverage reports
 
 Example usage:
@@ -124,7 +134,7 @@ Example usage:
 .. code-block:: bash
 
     python manager.py run-tests --test-type unit
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage
 
 
 Available Commands
@@ -133,49 +143,48 @@ Available Commands
 run-tests
 -------------------------------------------------------------------------------
 
-Execute test suites with flexible options:
+Execute unittest-based test suites with flexible options:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
-* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``, ``integration``, ``functional``)
-* ``--pattern``: File pattern to match test files (e.g., ``*.py``, ``test_*.py``). Works with both engines.
+* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``,
+  ``integration``, ``functional``). Default: ``unit``
+* ``--pattern``: File pattern to match test files (e.g., ``*.py``,
+  ``test_*.py``). Defaults to multi-pattern discovery.
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Run unit tests with unittest (default)
+    # Run unit tests (default)
     python manager.py run-tests --test-type unit
 
-    # Run integration tests with pytest
-    python manager.py run-tests --engine pytest --test-type integration
+    # Run integration tests
+    python manager.py run-tests --test-type integration
 
-    # Run tests with custom pattern
-    python manager.py run-tests --test-type functional --pattern "test_*.py"
+    # Run tests with a custom file pattern
+    python manager.py run-tests --test-type functional --pattern "*.py"
 
-    # Run all tests in a custom folder
+    # Run tests in a custom folder
     python manager.py run-tests --test-type "custom_folder"
 
 
 run-coverage
 -------------------------------------------------------------------------------
 
-Generate code coverage reports:
+Generate code coverage reports across all test directories:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
+* ``--save-report``: Save HTML and data coverage reports to disk.
+  Default: ``True``
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Generate coverage with unittest
     python manager.py run-coverage
-
-    # Generate coverage with pytest
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage --save-report false
 
 
 Quick Start
@@ -217,78 +226,32 @@ Tests and Coverage
 
     python manager.py run-tests --test-type unit
     python manager.py run-tests --test-type integration
-    python manager.py run-tests --test-type "another folder that contains test cases under ./tests"
     python manager.py run-tests --test-type functional --pattern "*.py"
+    python manager.py run-coverage
 
 
-Using PyTest
+Using pytest directly
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The `unittest` framework cannot discover or run pytest-style tests, it is designed to
-discover and run tests that are subclasses of `unittest.TestCase` and follow its
-conventions. Pytest-style tests (i.e., functions named test_* that are not inside a
-`unittest.TestCase` class, or tests using pytest fixtures, parametrize, etc.) are not
-recognized by unittest's discovery mechanism, `unittest` will simply ignore standalone
-test functions and any pytest-specific features...
-
-That's why you can use PyTest if required.
+``unittest`` cannot discover standalone ``test_*`` functions or use pytest
+fixtures. If your project relies on those features, invoke ``pytest`` directly:
 
 .. code-block:: bash
 
-    python manager.py run-tests --engine pytest
+    pytest tests/unit/
+    pytest -n auto --cov=your_package --cov-report=html
 
-..
-
-Test coverage
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Install ``pytest`` via ``pip`` or through ``core-dev-tools``:
 
 .. code-block:: bash
 
-    python manager.py run-coverage                          # For `unittest` framework...
-    python manager.py run-coverage --engine pytest          # For `PyTest`...
-    pytest -n auto --cov=core_tests --cov-report=html       # Direct `pytest` execution...
+    pip install pytest pytest-xdist pytest-cov
+    # or
+    pip install ".[dev]"  # if core-dev-tools includes pytest
 
 ..
 
 
-Best Practices
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-When working with pytest, consider these optimization strategies:
-
-1. **Use parallel execution for independent tests:**
-
-   .. code-block:: bash
-
-       pytest -n auto
-
-   ..
-
-2. **Run fast unit tests first during development:**
-
-   .. code-block:: bash
-
-       pytest tests/unit/ -n auto
-
-   ..
-
-3. **Run functional tests with limited parallelism:**
-
-   .. code-block:: bash
-
-       pytest tests/functional/ -n 2  # Avoid AWS rate limits
-
-   ..
-
-4. **Use markers to run specific test subsets:**
-
-   .. code-block:: bash
-
-       pytest -m "unit and not slow" -n auto
-
-   ..
-
-
 Contributing
 ===============================================================================
 
@@ -297,7 +260,7 @@ Contributions are welcome! Please:
 1. Fork the repository
 2. Create a feature branch
 3. Write tests for new functionality
-4. Ensure all tests pass: ``pytest -n auto``
+4. Ensure all tests pass: ``python manager.py run-tests --test-type unit``
 5. Run linting: ``pylint core_tests``
 6. Run security checks: ``bandit -r core_tests``
 7. Submit a pull request

{core_tests-2.0.4 → core_tests-2.1.0}/README.rst

@@ -1,11 +1,18 @@
 core-tests
 ===============================================================================
 
-This project contains basic elements for testing purposes and the ability 
-to run (via console commands) tests and code coverage (unittest-based). This way, we can 
-stick to the `DRY -- Don't Repeat Yourself` principle and avoid code duplication
-in each python project where tests coverage and tests execution are
-expected...
+A reusable library that provides CLI commands for running ``unittest``-based
+tests and generating code coverage reports. It wraps Python's built-in
+``unittest`` framework and ``coverage`` into a ``Click`` command group so
+consuming projects can use ``python manager.py run-tests`` and
+``python manager.py run-coverage`` without duplicating that logic across
+every project in the ecosystem.
+
+This library is intentionally scoped to ``unittest`` and ``coverage``.
+If your project requires ``pytest``-specific features (fixtures, parametrize,
+plugins, parallel execution), install ``pytest`` directly or via
+``core-dev-tools`` and invoke it standalone — it is a better fit for that use
+case than routing it through this abstraction layer.
 
 ===============================================================================
 
@@ -40,32 +47,35 @@ Install from PyPI using pip:
 .. code-block:: bash
 
     pip install core-tests
-
-Or using uv:
-
-.. code-block:: bash
-
-    uv pip install core-tests
+    uv pip install core-tests  # Or using UV...
 
 
 Features
 ===============================================================================
 
-* **Dual Test Engine Support**: Run tests using either `unittest` or `pytest` frameworks
-* **Flexible Test Discovery**: Supports multiple file patterns:
-    - `test_*.py` (standard pattern)
-    - `*_test.py` (alternative pattern)
-    - `tests_*.py` (custom pattern)
-* **Custom Pattern Support**: Specify custom file patterns using the `--pattern` flag
-* **Test Organization**: Run tests by type (unit, integration, functional, etc.)
-* **Coverage Reports**: Generate coverage reports with both frameworks
-* **CLI Integration**: Easy integration via Click command collections
+* **Unified CLI abstraction**: Expose ``run-tests`` and ``run-coverage`` in any
+  project without duplicating boilerplate — just wire ``cli_tests`` into your
+  ``CommandCollection``.
+* **Flexible Test Discovery**: Supports multiple file patterns out of the box:
+
+    - ``test_*.py`` (standard pattern)
+    - ``*_test.py`` (alternative pattern)
+    - ``tests_*.py`` (custom pattern)
+
+* **Custom Pattern Support**: Override discovery with ``--pattern`` for
+  non-standard file layouts.
+* **Test Organization**: Target specific test directories (unit, integration,
+  functional, etc.) via ``--test-type``.
+* **Branch Coverage Reports**: Generate branch-level coverage reports and
+  optional HTML output.
+* **DRY principle**: One implementation shared across all projects in the
+  ecosystem.
 
 
 How to Use
 ===============================================================================
 
-Create a ``manager.py`` file in your project root to integrate 
+Create a ``manager.py`` file in your project root to integrate
 the test commands:
 
 .. code-block:: python
@@ -80,7 +90,7 @@ the test commands:
 
 This setup provides two commands:
 
-* ``run-tests``: Execute test suites with unittest or pytest
+* ``run-tests``: Execute unittest-based test suites
 * ``run-coverage``: Generate code coverage reports
 
 Example usage:
@@ -88,7 +98,7 @@ Example usage:
 .. code-block:: bash
 
     python manager.py run-tests --test-type unit
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage
 
 
 Available Commands
@@ -97,49 +107,48 @@ Available Commands
 run-tests
 -------------------------------------------------------------------------------
 
-Execute test suites with flexible options:
+Execute unittest-based test suites with flexible options:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
-* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``, ``integration``, ``functional``)
-* ``--pattern``: File pattern to match test files (e.g., ``*.py``, ``test_*.py``). Works with both engines.
+* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``,
+  ``integration``, ``functional``). Default: ``unit``
+* ``--pattern``: File pattern to match test files (e.g., ``*.py``,
+  ``test_*.py``). Defaults to multi-pattern discovery.
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Run unit tests with unittest (default)
+    # Run unit tests (default)
     python manager.py run-tests --test-type unit
 
-    # Run integration tests with pytest
-    python manager.py run-tests --engine pytest --test-type integration
+    # Run integration tests
+    python manager.py run-tests --test-type integration
 
-    # Run tests with custom pattern
-    python manager.py run-tests --test-type functional --pattern "test_*.py"
+    # Run tests with a custom file pattern
+    python manager.py run-tests --test-type functional --pattern "*.py"
 
-    # Run all tests in a custom folder
+    # Run tests in a custom folder
     python manager.py run-tests --test-type "custom_folder"
 
 
 run-coverage
 -------------------------------------------------------------------------------
 
-Generate code coverage reports:
+Generate code coverage reports across all test directories:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
+* ``--save-report``: Save HTML and data coverage reports to disk.
+  Default: ``True``
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Generate coverage with unittest
     python manager.py run-coverage
-
-    # Generate coverage with pytest
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage --save-report false
 
 
 Quick Start
@@ -181,78 +190,32 @@ Tests and Coverage
 
     python manager.py run-tests --test-type unit
     python manager.py run-tests --test-type integration
-    python manager.py run-tests --test-type "another folder that contains test cases under ./tests"
     python manager.py run-tests --test-type functional --pattern "*.py"
+    python manager.py run-coverage
 
 
-Using PyTest
+Using pytest directly
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The `unittest` framework cannot discover or run pytest-style tests, it is designed to
-discover and run tests that are subclasses of `unittest.TestCase` and follow its
-conventions. Pytest-style tests (i.e., functions named test_* that are not inside a
-`unittest.TestCase` class, or tests using pytest fixtures, parametrize, etc.) are not
-recognized by unittest's discovery mechanism, `unittest` will simply ignore standalone
-test functions and any pytest-specific features...
-
-That's why you can use PyTest if required.
+``unittest`` cannot discover standalone ``test_*`` functions or use pytest
+fixtures. If your project relies on those features, invoke ``pytest`` directly:
 
 .. code-block:: bash
 
-    python manager.py run-tests --engine pytest
+    pytest tests/unit/
+    pytest -n auto --cov=your_package --cov-report=html
 
-..
-
-Test coverage
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Install ``pytest`` via ``pip`` or through ``core-dev-tools``:
 
 .. code-block:: bash
 
-    python manager.py run-coverage                          # For `unittest` framework...
-    python manager.py run-coverage --engine pytest          # For `PyTest`...
-    pytest -n auto --cov=core_tests --cov-report=html       # Direct `pytest` execution...
+    pip install pytest pytest-xdist pytest-cov
+    # or
+    pip install ".[dev]"  # if core-dev-tools includes pytest
 
 ..
 
 
-Best Practices
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-When working with pytest, consider these optimization strategies:
-
-1. **Use parallel execution for independent tests:**
-
-   .. code-block:: bash
-
-       pytest -n auto
-
-   ..
-
-2. **Run fast unit tests first during development:**
-
-   .. code-block:: bash
-
-       pytest tests/unit/ -n auto
-
-   ..
-
-3. **Run functional tests with limited parallelism:**
-
-   .. code-block:: bash
-
-       pytest tests/functional/ -n 2  # Avoid AWS rate limits
-
-   ..
-
-4. **Use markers to run specific test subsets:**
-
-   .. code-block:: bash
-
-       pytest -m "unit and not slow" -n auto
-
-   ..
-
-
 Contributing
 ===============================================================================
 
@@ -261,7 +224,7 @@ Contributions are welcome! Please:
 1. Fork the repository
 2. Create a feature branch
 3. Write tests for new functionality
-4. Ensure all tests pass: ``pytest -n auto``
+4. Ensure all tests pass: ``python manager.py run-tests --test-type unit``
 5. Run linting: ``pylint core_tests``
 6. Run security checks: ``bandit -r core_tests``
 7. Submit a pull request
@@ -292,4 +255,4 @@ For questions or support, please open an issue on GitLab or contact the maintain
 Authors
 ===============================================================================
 
-* **Alejandro Cora González** - *Initial work* - alek.cora.glez@gmail.com
+* **Alejandro Cora González** - *Initial work* - alek.cora.glez@gmail.com

core_tests-2.1.0/core_tests/__init__.py

@@ -0,0 +1,24 @@
+# -*- coding: utf-8 -*-
+
+"""
+Provides common elements for testing purposes.
+"""
+
+from importlib.metadata import PackageNotFoundError
+from importlib.metadata import version
+
+from core_tests.tests.base import BaseTestCase
+from core_tests.tests.runner import cli_tests
+
+try:
+    __version__ = version("core-tests")
+
+except PackageNotFoundError:
+    __version__ = "unknown"
+
+
+__all__ = [
+    "__version__",
+    "BaseTestCase",
+    "cli_tests",
+]

core_tests-2.1.0/core_tests/tests/runner.py

@@ -0,0 +1,153 @@
+# -*- coding: utf-8 -*-
+
+"""
+This module provides a group of CLI commands that abstract unittest-based
+test execution and code coverage measurement. Consuming projects import
+``cli_tests`` and wire it into their own ``CommandCollection`` to expose
+``run-tests`` and ``run-coverage`` without duplicating this logic.
+
+This library is intentionally scoped to ``unittest`` and ``coverage``. If your
+project requires pytest-specific features (fixtures, parametrize, plugins),
+install ``pytest`` directly or via ``core-dev-tools`` and invoke it standalone.
+
+**Test File Discovery:**
+
+By default, (``tests_*.py``), ``run-tests`` runs discovery across all three
+built-in patterns: ``test_*.py``, ``*_test.py``, and ``tests_*.py``.
+Supply ``--pattern`` with any other glob to target a specific naming
+convention instead.
+
+Tests that connect to real external services should use a naming convention
+that falls outside these patterns (e.g. ``check_*.py``) so they are not
+picked up automatically.
+
+**Available Commands:**
+
+  * ``python manager.py run-tests``
+  * ``python manager.py run-tests --test-type unit``
+  * ``python manager.py run-tests --test-type integration``
+  * ``python manager.py run-tests --test-type functional --pattern "*.py"``
+  * ``python manager.py run-coverage``
+"""
+
+from __future__ import annotations
+
+import logging
+import os
+import sys
+import typing
+from unittest import TestCase
+from unittest import TestLoader
+from unittest import TestSuite
+from unittest import TextTestRunner
+
+from click import echo, option
+from click.decorators import group
+from coverage import coverage, CoverageException
+
+patterns = [
+    "test_*.py",
+    "*_test.py",
+    "tests_*.py",
+]
+
+
+@group()
+def cli_tests():
+    """
+    Group of commands related to tests.
+    """
+
+
+@cli_tests.command("run-tests")
+@option("-t", "--test-type", "test_type", default="unit")
+@option("-p", "--pattern", "pattern", default="tests_*.py")
+def run_tests(test_type: str, pattern: str) -> None:
+    """
+    Runs unittest-based tests in a specific directory.
+
+    :param test_type: Directory name under ./tests/ (e.g., 'unit', 'integration', 'functional').
+    :param pattern: File glob pattern passed to ``TestLoader.discover``.
+
+    Pattern Usage:
+        - Default ``tests_*.py`` runs discovery across all three built-in
+          patterns: ``test_*.py``, ``*_test.py``, and ``tests_*.py``.
+        - Any other glob (e.g. ``test*.py``, ``*_test.py``, ``*.py``) runs a
+          single ``TestLoader.discover`` call with that pattern.
+    """
+
+    if not os.path.exists(f"./tests/{test_type}"):
+        echo(f"The directory: {test_type} does not exist under ./tests!", err=True)
+        sys.exit(1)
+
+    if test_type == "unit":
+        # Just removing verbosity from unit tests...
+        level = os.getenv("LOGGER_LEVEL_FOR_TEST", str(logging.ERROR))
+        os.environ["LOGGER_LEVEL"] = level
+
+    all_tests: typing.List[TestCase | TestSuite] = []
+
+    if pattern != "tests_*.py":
+        tests = TestLoader().discover(f"./tests/{test_type}", pattern=pattern)
+        all_tests.extend(tests)
+
+    else:
+        for pattern_glob in patterns:
+            tests = TestLoader().discover(f"./tests/{test_type}", pattern=pattern_glob)
+            all_tests.extend(tests)
+
+    result = TextTestRunner(verbosity=2).run(TestSuite(all_tests))
+    if not result.wasSuccessful():
+        sys.exit(1)
+
+
+@cli_tests.command("run-coverage")
+@option("-s", "--save-report", "save_report", default=True)
+def run_coverage(save_report: bool) -> None:
+    """
+    Runs all tests across all test directories and generates a coverage report.
+
+    :param save_report: Whether to save HTML and data coverage reports to disk.
+    :type save_report: bool
+
+    Coverage Analysis:
+      - Runs tests with branch coverage enabled.
+      - Analyzes all source files in current directory.
+      - Generates console report summary.
+      - Optionally saves HTML report (default: True).
+
+    File Discovery:
+        Automatically finds files matching: ``test_*.py``, ``*_test.py``, ``tests_*.py``
+        across all subdirectories under ``./tests/``. It means that functional or integration
+        tests that connect to real services should be named with other pattern,
+        like ``check_aws_integration``.
+    """
+
+    os.environ["LOGGER_LEVEL"] = os.getenv("LOGGER_LEVEL_FOR_TEST", str(logging.ERROR))
+    coverage_ = coverage(branch=True, source=["."])
+    coverage_.start()
+
+    all_tests: typing.List[TestCase | TestSuite] = []
+    for pattern_glob in patterns:
+        tests = TestLoader().discover("./tests", pattern=pattern_glob)
+        all_tests.extend(tests)
+
+    result = TextTestRunner(verbosity=3).run(TestSuite(all_tests))
+    if not result.wasSuccessful():
+        sys.exit(1)
+
+    coverage_.stop()
+
+    try:
+        echo("Coverage Summary:")
+        coverage_.report()
+
+        if save_report:
+            coverage_.save()
+            coverage_.html_report()
+
+        coverage_.erase()
+
+    except CoverageException as error:
+        echo(error)
+        sys.exit(1)

{core_tests-2.0.4 → core_tests-2.1.0}/core_tests.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: core-tests
-Version: 2.0.4
+Version: 2.1.0
 Summary: It contains common elements for testing purposes...
 Author-email: Alejandro Cora González <alek.cora.glez@gmail.com>
 Maintainer: Alejandro Cora González
@@ -22,26 +22,33 @@ 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 :: Implementation :: PyPy
 Requires-Python: >=3.9
 Description-Content-Type: text/x-rst
 License-File: LICENSE
 Requires-Dist: click>=8.1.8
 Requires-Dist: coverage>=7.7.1
 Requires-Dist: environs>=14.1.1
-Requires-Dist: pytest>=7.4.0
-Requires-Dist: pytest-xdist>=3.5.0
 Provides-Extra: dev
-Requires-Dist: core-dev-tools>=1.0.1; extra == "dev"
+Requires-Dist: core-dev-tools>=2.0.0; extra == "dev"
 Dynamic: license-file
 
 core-tests
 ===============================================================================
 
-This project contains basic elements for testing purposes and the ability 
-to run (via console commands) tests and code coverage (unittest-based). This way, we can 
-stick to the `DRY -- Don't Repeat Yourself` principle and avoid code duplication
-in each python project where tests coverage and tests execution are
-expected...
+A reusable library that provides CLI commands for running ``unittest``-based
+tests and generating code coverage reports. It wraps Python's built-in
+``unittest`` framework and ``coverage`` into a ``Click`` command group so
+consuming projects can use ``python manager.py run-tests`` and
+``python manager.py run-coverage`` without duplicating that logic across
+every project in the ecosystem.
+
+This library is intentionally scoped to ``unittest`` and ``coverage``.
+If your project requires ``pytest``-specific features (fixtures, parametrize,
+plugins, parallel execution), install ``pytest`` directly or via
+``core-dev-tools`` and invoke it standalone — it is a better fit for that use
+case than routing it through this abstraction layer.
 
 ===============================================================================
 
@@ -76,32 +83,35 @@ Install from PyPI using pip:
 .. code-block:: bash
 
     pip install core-tests
-
-Or using uv:
-
-.. code-block:: bash
-
-    uv pip install core-tests
+    uv pip install core-tests  # Or using UV...
 
 
 Features
 ===============================================================================
 
-* **Dual Test Engine Support**: Run tests using either `unittest` or `pytest` frameworks
-* **Flexible Test Discovery**: Supports multiple file patterns:
-    - `test_*.py` (standard pattern)
-    - `*_test.py` (alternative pattern)
-    - `tests_*.py` (custom pattern)
-* **Custom Pattern Support**: Specify custom file patterns using the `--pattern` flag
-* **Test Organization**: Run tests by type (unit, integration, functional, etc.)
-* **Coverage Reports**: Generate coverage reports with both frameworks
-* **CLI Integration**: Easy integration via Click command collections
+* **Unified CLI abstraction**: Expose ``run-tests`` and ``run-coverage`` in any
+  project without duplicating boilerplate — just wire ``cli_tests`` into your
+  ``CommandCollection``.
+* **Flexible Test Discovery**: Supports multiple file patterns out of the box:
+
+    - ``test_*.py`` (standard pattern)
+    - ``*_test.py`` (alternative pattern)
+    - ``tests_*.py`` (custom pattern)
+
+* **Custom Pattern Support**: Override discovery with ``--pattern`` for
+  non-standard file layouts.
+* **Test Organization**: Target specific test directories (unit, integration,
+  functional, etc.) via ``--test-type``.
+* **Branch Coverage Reports**: Generate branch-level coverage reports and
+  optional HTML output.
+* **DRY principle**: One implementation shared across all projects in the
+  ecosystem.
 
 
 How to Use
 ===============================================================================
 
-Create a ``manager.py`` file in your project root to integrate 
+Create a ``manager.py`` file in your project root to integrate
 the test commands:
 
 .. code-block:: python
@@ -116,7 +126,7 @@ the test commands:
 
 This setup provides two commands:
 
-* ``run-tests``: Execute test suites with unittest or pytest
+* ``run-tests``: Execute unittest-based test suites
 * ``run-coverage``: Generate code coverage reports
 
 Example usage:
@@ -124,7 +134,7 @@ Example usage:
 .. code-block:: bash
 
     python manager.py run-tests --test-type unit
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage
 
 
 Available Commands
@@ -133,49 +143,48 @@ Available Commands
 run-tests
 -------------------------------------------------------------------------------
 
-Execute test suites with flexible options:
+Execute unittest-based test suites with flexible options:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
-* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``, ``integration``, ``functional``)
-* ``--pattern``: File pattern to match test files (e.g., ``*.py``, ``test_*.py``). Works with both engines.
+* ``--test-type``: Folder name under ``./tests`` directory (e.g., ``unit``,
+  ``integration``, ``functional``). Default: ``unit``
+* ``--pattern``: File pattern to match test files (e.g., ``*.py``,
+  ``test_*.py``). Defaults to multi-pattern discovery.
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Run unit tests with unittest (default)
+    # Run unit tests (default)
     python manager.py run-tests --test-type unit
 
-    # Run integration tests with pytest
-    python manager.py run-tests --engine pytest --test-type integration
+    # Run integration tests
+    python manager.py run-tests --test-type integration
 
-    # Run tests with custom pattern
-    python manager.py run-tests --test-type functional --pattern "test_*.py"
+    # Run tests with a custom file pattern
+    python manager.py run-tests --test-type functional --pattern "*.py"
 
-    # Run all tests in a custom folder
+    # Run tests in a custom folder
     python manager.py run-tests --test-type "custom_folder"
 
 
 run-coverage
 -------------------------------------------------------------------------------
 
-Generate code coverage reports:
+Generate code coverage reports across all test directories:
 
 **Options:**
 
-* ``--engine``: Test engine to use (``unittest`` or ``pytest``). Default: ``unittest``
+* ``--save-report``: Save HTML and data coverage reports to disk.
+  Default: ``True``
 
 **Examples:**
 
 .. code-block:: bash
 
-    # Generate coverage with unittest
     python manager.py run-coverage
-
-    # Generate coverage with pytest
-    python manager.py run-coverage --engine pytest
+    python manager.py run-coverage --save-report false
 
 
 Quick Start
@@ -217,78 +226,32 @@ Tests and Coverage
 
     python manager.py run-tests --test-type unit
     python manager.py run-tests --test-type integration
-    python manager.py run-tests --test-type "another folder that contains test cases under ./tests"
     python manager.py run-tests --test-type functional --pattern "*.py"
+    python manager.py run-coverage
 
 
-Using PyTest
+Using pytest directly
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The `unittest` framework cannot discover or run pytest-style tests, it is designed to
-discover and run tests that are subclasses of `unittest.TestCase` and follow its
-conventions. Pytest-style tests (i.e., functions named test_* that are not inside a
-`unittest.TestCase` class, or tests using pytest fixtures, parametrize, etc.) are not
-recognized by unittest's discovery mechanism, `unittest` will simply ignore standalone
-test functions and any pytest-specific features...
-
-That's why you can use PyTest if required.
+``unittest`` cannot discover standalone ``test_*`` functions or use pytest
+fixtures. If your project relies on those features, invoke ``pytest`` directly:
 
 .. code-block:: bash
 
-    python manager.py run-tests --engine pytest
+    pytest tests/unit/
+    pytest -n auto --cov=your_package --cov-report=html
 
-..
-
-Test coverage
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Install ``pytest`` via ``pip`` or through ``core-dev-tools``:
 
 .. code-block:: bash
 
-    python manager.py run-coverage                          # For `unittest` framework...
-    python manager.py run-coverage --engine pytest          # For `PyTest`...
-    pytest -n auto --cov=core_tests --cov-report=html       # Direct `pytest` execution...
+    pip install pytest pytest-xdist pytest-cov
+    # or
+    pip install ".[dev]"  # if core-dev-tools includes pytest
 
 ..
 
 
-Best Practices
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-When working with pytest, consider these optimization strategies:
-
-1. **Use parallel execution for independent tests:**
-
-   .. code-block:: bash
-
-       pytest -n auto
-
-   ..
-
-2. **Run fast unit tests first during development:**
-
-   .. code-block:: bash
-
-       pytest tests/unit/ -n auto
-
-   ..
-
-3. **Run functional tests with limited parallelism:**
-
-   .. code-block:: bash
-
-       pytest tests/functional/ -n 2  # Avoid AWS rate limits
-
-   ..
-
-4. **Use markers to run specific test subsets:**
-
-   .. code-block:: bash
-
-       pytest -m "unit and not slow" -n auto
-
-   ..
-
-
 Contributing
 ===============================================================================
 
@@ -297,7 +260,7 @@ Contributions are welcome! Please:
 1. Fork the repository
 2. Create a feature branch
 3. Write tests for new functionality
-4. Ensure all tests pass: ``pytest -n auto``
+4. Ensure all tests pass: ``python manager.py run-tests --test-type unit``
 5. Run linting: ``pylint core_tests``
 6. Run security checks: ``bandit -r core_tests``
 7. Submit a pull request

core_tests-2.1.0/core_tests.egg-info/requires.txt

@@ -0,0 +1,6 @@
+click>=8.1.8
+coverage>=7.7.1
+environs>=14.1.1
+
+[dev]
+core-dev-tools>=2.0.0

{core_tests-2.0.4 → core_tests-2.1.0}/pyproject.toml

@@ -8,7 +8,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "core-tests"
-version = "2.0.4"
+version = "2.1.0"
 
 description = """It contains common elements for testing purposes..."""
 
@@ -38,19 +38,19 @@ classifiers = [
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: Implementation :: PyPy",
 ]
 
 dependencies = [
     "click>=8.1.8",
     "coverage>=7.7.1",
     "environs>=14.1.1",
-    "pytest>=7.4.0",
-    "pytest-xdist>=3.5.0",
 ]
 
 [project.optional-dependencies]
 dev = [
-    "core-dev-tools>=1.0.1",
+    "core-dev-tools>=2.0.0",
 ]
 
 [project.urls]
@@ -60,5 +60,8 @@ Documentation = "https://core-tests.readthedocs.io/en/latest/"
 Issues = "https://gitlab.com/bytecode-solutions/core/core-tests/-/issues"
 Changelog = "https://gitlab.com/bytecode-solutions/core/core-tests/-/blob/master/CHANGELOG.md"
 
+[tool.pytest.ini_options]
+python_files = ["test_*.py", "*_test.py", "tests_*.py"]
+
 [tool.setuptools.package-data]
 "core_tests" = ["py.typed"]

core_tests-2.0.4/core_tests/tests/runner.py

@@ -1,226 +0,0 @@
-# -*- coding: utf-8 -*-
-
-"""
-This module provides a group of commands related to tests, this way we
-avoid defining them in each project that requires them.
-
-**Test File Discovery:**
-
-Automatically discovers test files matching these patterns:
-  * ``test_*.py`` (standard pytest/unittest pattern)
-  * ``*_test.py`` (standard pytest pattern)
-  * ``tests_*.py`` (legacy pattern support)
-
-Available Commands:
-  * python manager.py run-tests --test-type unit
-  * python manager.py run-tests --test-type integration
-  * python manager.py run-tests --test-type functional
-  * python manager.py run-tests --engine pytest
-  * python manager.py run-tests --pattern "test_specific"
-  * python manager.py run-coverage
-  * python manager.py run-coverage --engine pytest
-"""
-
-from __future__ import annotations
-
-import glob
-import logging
-import os
-import sys
-import typing
-from unittest import TestCase
-from unittest import TestLoader
-from unittest import TestSuite
-from unittest import TextTestRunner
-
-import pytest
-from click import echo, option
-from click.decorators import group
-from coverage import coverage, CoverageException
-
-patterns = [
-    "test_*.py",
-    "*_test.py",
-    "tests_*.py",
-]
-
-
-@group()
-def cli_tests():
-    """
-    Group of commands related to tests.
-    """
-
-
-@cli_tests.command("run-tests")
-@option("-t", "--test-type", "test_type", default="unit")
-@option("-p", "--pattern", "pattern", default="tests*.py")
-@option("-e", "--engine", "engine", default="unittest")
-def run_tests(test_type: str, pattern: str, engine: str) -> None:
-    """
-    Runs tests in a specific directory using the specified engine.
-
-    :param test_type: Directory name under ./tests/ (e.g., 'unit', 'integration').
-    :param pattern: File pattern for discovery or test name pattern for filtering.
-    :param engine: Test engine to use ('unittest' or 'pytest').
-
-    File Discovery:
-        Automatically finds files matching: `test_*.py`, `*_test.py`, `tests_*.py`.
-
-    Pattern Usage:
-        - File patterns (*.py): Used for file discovery (pytest only).
-        - Test names: Used with -k option for test filtering (pytest only).
-        - Default: 'tests*.py' (backward compatibility).
-    """
-
-    validate_engines(engine)
-    if not os.path.exists(f"./tests/{test_type}"):
-        echo(f"The directory: {test_type} does not exist under ./tests!", err=True)
-        sys.exit(1)
-
-    if test_type == "unit":
-        # Just removing verbosity from unit tests...
-        level = os.getenv("LOGGER_LEVEL_FOR_TEST", str(logging.ERROR))
-        os.environ["LOGGER_LEVEL"] = level
-
-    if engine == "pytest":
-        test_path = f"./tests/{test_type}"
-
-        # Determine if pattern is for file discovery or test filtering
-        is_file_pattern = "*" in pattern and pattern.endswith(".py")
-
-        # Find all test files using appropriate patterns
-        test_files = []
-        if is_file_pattern and pattern != "tests_*.py":
-            # Use custom file pattern for discovery
-            test_files.extend(glob.glob(f"{test_path}/{pattern}"))
-
-        else:
-            # Use default patterns for file discovery
-            for pattern_glob in patterns:
-                test_files.extend(glob.glob(f"{test_path}/{pattern_glob}"))
-
-        if not test_files:
-            echo(f"No test files found in {test_path}", err=True)
-            sys.exit(1)
-
-        # Use specific test files instead of directory discovery
-        args = test_files + ["-v"]
-
-        # If pattern is for test name filtering (not file pattern), use -k
-        if not is_file_pattern and pattern != "tests_*.py":
-            args.extend(["-k", pattern])
-
-        exit_code = pytest.main(args)
-        if exit_code != 0:
-            sys.exit(exit_code)
-
-    else:
-        # Determine if pattern is for file discovery or test filtering
-        is_file_pattern = "*" in pattern and pattern.endswith(".py")
-
-        # Use the same patterns as pytest for consistency
-        all_tests: typing.List[TestCase | TestSuite] = []
-        if is_file_pattern and pattern != "tests_*.py":
-            # Use custom file pattern for discovery
-            tests = TestLoader().discover(f"./tests/{test_type}", pattern=pattern)
-            all_tests.extend(tests)
-        else:
-            # Use default patterns for file discovery
-            for pattern_glob in patterns:
-                tests = TestLoader().discover(f"./tests/{test_type}", pattern=pattern_glob)
-                all_tests.extend(tests)
-
-        # Combine all discovered tests into a single suite
-        combined_suite = TestSuite(all_tests)
-        result = TextTestRunner(verbosity=2).run(combined_suite)
-        if not result.wasSuccessful():
-            sys.exit(1)
-
-
-@cli_tests.command("run-coverage")
-@option("-s", "--save-report", "save_report", default=True)
-@option("-e", "--engine", "engine", default="unittest")
-def run_coverage(save_report: bool, engine: str) -> None:
-    """
-    Runs all tests across all test directories and generates a coverage report.
-
-    :param save_report: Whether to save HTML and data coverage reports to disk.
-    :type save_report: bool
-    :param engine: Test engine to use ('unittest' or 'pytest').
-    :type engine: str
-
-    Coverage Analysis:
-        - Runs tests with branch coverage enabled.
-        - Analyzes all source files in current directory.
-        - Generates console report summary.
-        - Optionally saves HTML report (default: True).
-
-    File Discovery:
-        Automatically finds files matching: `test_*.py`, `*_test.py`, `tests_*.py`.
-        across all subdirectories under `./tests/`.
-    """
-
-    validate_engines(engine)
-    os.environ["LOGGER_LEVEL"] = os.getenv("LOGGER_LEVEL_FOR_TEST", str(logging.ERROR))
-    coverage_ = coverage(branch=True, source=["."])
-    coverage_.start()
-
-    if engine == "pytest":
-        # Finding all test files using multiple patterns
-        # across all test directories...
-        test_files = []
-        for pattern_glob in patterns:
-            test_files.extend(glob.glob(f"./tests/**/{pattern_glob}", recursive=True))
-
-        if test_files:
-            exit_code = pytest.main(test_files + ["-v"])
-        else:
-            exit_code = pytest.main(["./tests", "-v"])
-
-        if exit_code != 0:
-            sys.exit(exit_code)
-
-    else:
-        all_tests: typing.List[TestCase | TestSuite] = []
-        for pattern_glob in patterns:
-            tests = TestLoader().discover("./tests", pattern=pattern_glob)
-            all_tests.extend(tests)
-
-        result = TextTestRunner(verbosity=3).run(TestSuite(all_tests))
-        if not result.wasSuccessful():
-            sys.exit(1)
-
-    coverage_.stop()
-
-    try:
-        echo("Coverage Summary:")
-        coverage_.report()
-
-        if save_report:
-            coverage_.save()
-            coverage_.html_report()
-
-        coverage_.erase()
-
-    except CoverageException as error:
-        echo(error)
-        sys.exit(1)
-
-
-def validate_engines(engine: str) -> None:
-    """
-    Validates that the specified test engine is supported.
-
-    :param engine: The test engine name to validate.
-    :raises: SystemExit: If the engine is not in the list of valid engines.
-
-    Supported Engines:
-    - 'unittest': Python's built-in unittest framework.
-    - 'pytest': Third-party pytest framework.
-    """
-
-    _engines = ["unittest", "pytest"]
-    if engine not in _engines:
-        echo(f"Valid engines: {_engines}", err=True)
-        sys.exit(1)

core_tests-2.0.4/core_tests.egg-info/requires.txt

@@ -1,8 +0,0 @@
-click>=8.1.8
-coverage>=7.7.1
-environs>=14.1.1
-pytest>=7.4.0
-pytest-xdist>=3.5.0
-
-[dev]
-core-dev-tools>=1.0.1