fastsmtp-cli 0.7.0__tar.gz → 0.7.1__tar.gz

{fastsmtp_cli-0.7.0 → fastsmtp_cli-0.7.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: fastsmtp-cli
-Version: 0.7.0
+Version: 0.7.1
 Summary: Remote CLI client for FastSMTP server
 Project-URL: Homepage, https://jsenecal.github.io/fastsmtp/cli/fsmtp/
 Project-URL: Documentation, https://jsenecal.github.io/fastsmtp/cli/fsmtp/

{fastsmtp_cli-0.7.0 → fastsmtp_cli-0.7.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "fastsmtp-cli"
-version = "0.7.0"
+version = "0.7.1"
 description = "Remote CLI client for FastSMTP server"
 readme = "README.md"
 requires-python = ">=3.12"

{fastsmtp_cli-0.7.0 → fastsmtp_cli-0.7.1}/src/fastsmtp_cli/__init__.py

@@ -1,3 +1,3 @@
 """FastSMTP CLI - Remote CLI client for FastSMTP server."""
 
-__version__ = "0.7.0"
+__version__ = "0.7.1"

fastsmtp_cli-0.7.1/tests/conftest.py

@@ -0,0 +1,49 @@
+"""Shared test configuration for the CLI package.
+
+``test_api_contract`` imports ``fastsmtp.main`` to build the server's OpenAPI
+document, and that module resolves settings at import time. Without these
+variables the import raises before any fixture argument can supply them, so the
+contract tests error out whenever this package's tests run on their own rather
+than as part of the full suite.
+"""
+
+import os
+
+import pytest
+
+# Set required environment variables before any imports
+os.environ.setdefault("FASTSMTP_ROOT_API_KEY", "test_root_api_key_12345")
+os.environ.setdefault("FASTSMTP_DATABASE_URL", "sqlite+aiosqlite:///:memory:")
+
+CONSOLE_WIDTH = 80
+
+
+@pytest.fixture(autouse=True)
+def deterministic_console(monkeypatch):
+    """Render as if piped to an 80-column pipe, whatever terminal ran the suite.
+
+    ``fastsmtp_cli.output`` builds both consoles at module scope, so each one
+    resolves its colour system and its width from the environment on import.
+    Two variables then decide what every assertion in ``test_output`` sees:
+
+    * ``FORCE_COLOR`` - which editors and agent harnesses set routinely - makes
+      rich emit ANSI escapes even though pytest's captured stdout is no tty.
+    * ``COLUMNS`` decides whether a table cell is padded or truncated to an
+      ellipsis.
+
+    CI sets neither, so both were invisible there and failed a clean ``main``
+    on a developer's machine instead. See issue #159.
+
+    Pinning the attributes rather than deleting the environment variables is
+    deliberate: ``_color_system`` is resolved in ``Console.__init__`` and never
+    consulted again, so unsetting ``FORCE_COLOR`` from a fixture is already too
+    late for a console built at import time - and which module imported
+    ``output`` first is not something this file can order. Mutating the two
+    console objects in place reaches every reference to them, including the
+    ones ``test_output`` imported by value.
+    """
+    from fastsmtp_cli.output import console, error_console
+
+    for target in (console, error_console):
+        monkeypatch.setattr(target, "_color_system", None)
+        monkeypatch.setattr(target, "_width", CONSOLE_WIDTH)

{fastsmtp_cli-0.7.0 → fastsmtp_cli-0.7.1}/tests/test_output.py

@@ -6,6 +6,7 @@ import pytest
 from fastsmtp_cli.output import (
     _format_expiry,
     console,
+    error_console,
     field,
     format_datetime,
     format_deleted,
@@ -1390,3 +1391,33 @@ class TestServerTextEscaping:
         output = capsys.readouterr().out
         assert "(catch-all)" in output
         assert "[dim]" not in output
+
+
+class TestOutputIsEnvironmentIndependent:
+    """Rendering must not depend on the terminal the suite happens to run in.
+
+    Both consoles are module-level, so they resolve their colour system and
+    their width when ``output`` is imported - before any test runs, and from
+    whatever environment the developer has. Two variables leak in:
+
+    * ``FORCE_COLOR``, which editors and agent harnesses set routinely, makes
+      rich emit ANSI escapes even though pytest's captured stdout is not a
+      tty. Assertions here match plain substrings, so they meet
+      ``\\x1b[1m[\\x1b[0mfrom, to, subject`` instead of ``[from, to, subject]``.
+    * ``COLUMNS``, which decides whether a table cell is padded or truncated
+      to an ellipsis.
+
+    Both used to fail a clean ``main`` outside CI. See issue #159.
+    """
+
+    def test_stdout_carries_no_ansi_escapes(self, capsys):
+        print_info("hello")
+        assert "\x1b[" not in capsys.readouterr().out
+
+    def test_stderr_carries_no_ansi_escapes(self, capsys):
+        print_error("Invalid field 'x'. Valid fields: [from, to, subject]")
+        assert "\x1b[" not in capsys.readouterr().err
+
+    def test_both_consoles_are_pinned_to_a_known_width(self):
+        assert console.width == 80
+        assert error_console.width == 80

fastsmtp_cli-0.7.0/tests/conftest.py

@@ -1,14 +0,0 @@
-"""Shared test configuration for the CLI package.
-
-``test_api_contract`` imports ``fastsmtp.main`` to build the server's OpenAPI
-document, and that module resolves settings at import time. Without these
-variables the import raises before any fixture argument can supply them, so the
-contract tests error out whenever this package's tests run on their own rather
-than as part of the full suite.
-"""
-
-import os
-
-# Set required environment variables before any imports
-os.environ.setdefault("FASTSMTP_ROOT_API_KEY", "test_root_api_key_12345")
-os.environ.setdefault("FASTSMTP_DATABASE_URL", "sqlite+aiosqlite:///:memory:")