etlplus 0.16.7__tar.gz → 0.16.8__tar.gz

{etlplus-0.16.7 → etlplus-0.16.8}/CONTRIBUTING.md

@@ -14,7 +14,7 @@ email, or any other method with the owners of this repository before making a ch
   - [Type Checking](#type-checking)
   - [Typing Philosophy](#typing-philosophy)
   - [Testing](#testing)
-    - [Unit vs. Integration](#unit-vs-integration)
+    - [Unit vs. Smoke vs. Integration](#unit-vs-smoke-vs-integration)
     - [Where to put tests](#where-to-put-tests)
     - [Common patterns](#common-patterns)
 
@@ -104,9 +104,9 @@ class ExampleConfig:
 
 ## Testing
 
-### Unit vs. Integration
+### Unit vs. Smoke vs. Integration
 
-Use these guidelines to decide whether a test belongs in the unit or integration suite:
+Use these guidelines to decide whether a test belongs in the unit, smoke, or integration suite:
 
 - Unit tests (put under `tests/unit/`):
   - Exercise a single function or class in isolation (no orchestration across modules).
@@ -117,13 +117,19 @@ Use these guidelines to decide whether a test belongs in the unit or integration
 - Integration tests (put under `tests/integration/`):
   - Exercise end-to-end flows across modules and boundaries (CLI `main()`, `run()` pipeline orchestration, file connectors, API client pagination wiring).
   - Can use temporary files/directories, and stub network with fakes/mocks.
-  - Examples in this repo: CLI end-to-end, pipeline smoke tests, pagination strategy, runner defaults for pagination/rate limits, target URL composition.
+  - Examples in this repo: CLI end-to-end, pagination strategy, runner defaults for pagination/rate limits, target URL composition.
+
+- Smoke tests (put under `tests/smoke/`):
+  - Minimal end-to-end checks for core flows; very fast and stable.
+  - May touch temporary files but avoid external network calls.
+  - Examples in this repo: pipeline smoke tests.
 
 If a test calls `etlplus.cli.main()` or `etlplus.ops.run.run()`, it is integration by default.
 
 ### Where to put tests
 
 - Unit tests live in `tests/unit/` and should import and test specific functions/classes directly.
+- Smoke tests live in `tests/smoke/` and should focus on minimal end-to-end CLI/pipeline checks.
 - Integration tests live in `tests/integration/` and may simulate real usage using CLI argv, temporary files, and fake clients.
 - The `tests/integration/conftest.py` applies `@pytest.mark.integration` to all tests in that folder. You don’t need to add the marker per test.
 - Markers are declared in `pytest.ini`. Avoid introducing ad-hoc markers without adding them there.

{etlplus-0.16.7/etlplus.egg-info → etlplus-0.16.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: etlplus
-Version: 0.16.7
+Version: 0.16.8
 Summary: A Swiss Army knife for simple ETL operations
 Home-page: https://github.com/Dagitali/ETLPlus
 Author: ETLPlus Team
@@ -722,10 +722,12 @@ pytest tests/ -v
 
 #### Test Layers
 
-We split tests into two layers:
+We split tests into three layers:
 
 - **Unit (`tests/unit/`)**: single function or class, no real I/O, fast, uses stubs/monkeypatch
   (e.g. small helpers in `etlplus.utils`, transform + validate helpers).
+- **Smoke (`tests/smoke/`)**: minimal end-to-end checks for core flows; may touch temp files but
+  avoids external network calls.
 - **Integration (`tests/integration/`)**: end-to-end flows (CLI `main()`, pipeline `run()`,
   pagination + rate limit defaults, file/API connector interactions) may touch temp files and use
   fake clients.

{etlplus-0.16.7 → etlplus-0.16.8}/README.md

@@ -672,10 +672,12 @@ pytest tests/ -v
 
 #### Test Layers
 
-We split tests into two layers:
+We split tests into three layers:
 
 - **Unit (`tests/unit/`)**: single function or class, no real I/O, fast, uses stubs/monkeypatch
   (e.g. small helpers in `etlplus.utils`, transform + validate helpers).
+- **Smoke (`tests/smoke/`)**: minimal end-to-end checks for core flows; may touch temp files but
+  avoids external network calls.
 - **Integration (`tests/integration/`)**: end-to-end flows (CLI `main()`, pipeline `run()`,
   pagination + rate limit defaults, file/API connector interactions) may touch temp files and use
   fake clients.

{etlplus-0.16.7 → etlplus-0.16.8/etlplus.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: etlplus
-Version: 0.16.7
+Version: 0.16.8
 Summary: A Swiss Army knife for simple ETL operations
 Home-page: https://github.com/Dagitali/ETLPlus
 Author: ETLPlus Team
@@ -722,10 +722,12 @@ pytest tests/ -v
 
 #### Test Layers
 
-We split tests into two layers:
+We split tests into three layers:
 
 - **Unit (`tests/unit/`)**: single function or class, no real I/O, fast, uses stubs/monkeypatch
   (e.g. small helpers in `etlplus.utils`, transform + validate helpers).
+- **Smoke (`tests/smoke/`)**: minimal end-to-end checks for core flows; may touch temp files but
+  avoids external network calls.
 - **Integration (`tests/integration/`)**: end-to-end flows (CLI `main()`, pipeline `run()`,
   pagination + rate limit defaults, file/API connector interactions) may touch temp files and use
   fake clients.

{etlplus-0.16.7 → etlplus-0.16.8}/etlplus.egg-info/SOURCES.txt

@@ -174,6 +174,7 @@ examples/data/sample.json
 examples/data/sample.xml
 examples/data/sample.xsd
 examples/data/sample.yaml
+tests/README.md
 tests/__init__.py
 tests/conftest.py
 tests/integration/conftest.py
@@ -181,10 +182,10 @@ tests/integration/test_i_cli.py
 tests/integration/test_i_config_load.py
 tests/integration/test_i_examples_data_parity.py
 tests/integration/test_i_pagination_strategy.py
-tests/integration/test_i_pipeline_smoke.py
 tests/integration/test_i_run.py
 tests/integration/test_i_run_profile_pagination_defaults.py
 tests/integration/test_i_run_profile_rate_limit_defaults.py
+tests/smoke/test_s_pipeline.py
 tests/unit/conftest.py
 tests/unit/test_u_config.py
 tests/unit/test_u_main.py

etlplus-0.16.8/pytest.ini

@@ -0,0 +1,13 @@
+# pytest.ini
+# ETLPlus
+#
+# Copyright © 2025 Dagitali LLC. All rights reserved.
+
+[pytest]
+testpaths = tests/unit tests/smoke tests/integration
+addopts = -ra
+markers =
+    property: property-based tests (Hypothesis) for URL composition and encoding
+    smoke: fast end-to-end tests covering core flows
+    integration: tests that exercise multiple modules or external I/O boundaries
+    unit: tests that isolate individual modules or functions

etlplus-0.16.8/tests/README.md

@@ -0,0 +1,38 @@
+# Tests Overview
+
+ETLPlus uses three categories of tests. Each category lives in its own folder and is tagged with a
+pytest marker to make selection easy.
+
+## Unit tests (`tests/unit/`)
+
+- Scope: single function or class in isolation
+- I/O: no real file system or network I/O (use stubs/monkeypatch)
+- Speed: fast, deterministic
+- Marker: `unit`
+
+## Smoke tests (`tests/smoke/`)
+
+- Scope: minimal end-to-end sanity checks for core flows
+- I/O: may touch temp files; no external network calls
+- Speed: very fast; intended to catch obvious regressions
+- Marker: `smoke`
+
+## Integration tests (`tests/integration/`)
+
+- Scope: cross-module workflows and CLI/pipeline paths
+- I/O: may touch temp files; may use fakes/mocks for HTTP clients
+- Speed: slower than unit/smoke
+- Marker: `integration`
+
+## Running tests
+
+```bash
+pytest tests/unit
+pytest tests/smoke
+pytest tests/integration
+
+# Marker-based selection
+pytest -m unit
+pytest -m smoke
+pytest -m integration
+```

etlplus-0.16.7/tests/integration/test_i_pipeline_smoke.py → etlplus-0.16.8/tests/smoke/test_s_pipeline.py

@@ -1,9 +1,8 @@
 """
-:mod:`tests.integration.test_i_pipeline_smoke` module.
+:mod:`tests.smoke.test_s_pipeline` module.
 
-Pipeline smoke integration test suite exercising a minimal file→file job via
-the CLI (using the deprecated-free path). Parametrized to verify both empty
-and non-empty inputs.
+Smoke test suite exercising a minimal file→file job via the CLI. Parametrized
+to verify both empty and non-empty inputs.
 
 Notes
 -----
@@ -28,14 +27,14 @@ if TYPE_CHECKING:  # pragma: no cover - typing helpers only
 # SECTION: HELPERS ========================================================== #
 
 
-pytestmark = pytest.mark.integration
+pytestmark = pytest.mark.smoke
 
 
 # SECTION: TESTS ============================================================ #
 
 
-class TestPipelineSmoke:
-    """Integration test suite for file→file job via CLI."""
+class TestPipeline:
+    """Smoke test suite for file→file job via CLI."""
 
     @pytest.mark.parametrize(
         'data_in',

etlplus-0.16.7/pytest.ini

@@ -1,12 +0,0 @@
-# pytest.ini
-# ETLPlus
-#
-# Copyright © 2025 Dagitali LLC. All rights reserved.
-
-[pytest]
-testpaths = tests/unit tests/integration
-addopts = -ra
-markers =
-	property: property-based tests (Hypothesis) for URL composition and encoding
-	integration: tests that exercise multiple modules or external I/O boundaries
-    unit: tests that isolate individual modules or functions