ha-mcp-dev 8.4.3.dev2648__tar.gz → 8.4.3.dev2650__tar.gz

{ha_mcp_dev-8.4.3.dev2648/src/ha_mcp_dev.egg-info → ha_mcp_dev-8.4.3.dev2650}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 8.4.3.dev2648
+Version: 8.4.3.dev2650
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT

{ha_mcp_dev-8.4.3.dev2648 → ha_mcp_dev-8.4.3.dev2650}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "8.4.3.dev2648"
+version = "8.4.3.dev2650"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 # Upper bound widened to <3.15 so the package installs on Home Assistant's
@@ -258,36 +258,117 @@ ignore = [
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
-python_files = ["test_*.py", "*_test.py"]
+python_files = ["test_*.py"]
 python_classes = ["Test*"]
 python_functions = ["test_*"]
-# See tests/pytest.ini: an empty parametrize list is a guard that stopped
-# running, and the default mark hides it as a skip the summary ignores.
+# A parametrize list that resolves to nothing is a guard that silently stopped
+# running: pytest reports "got empty parameter set", and the summary counts it
+# as neither a failure nor a real skip. Make it a collection error instead.
 empty_parameter_set_mark = "fail_at_collect"
+
+# Command line options
 addopts = [
     "--strict-markers",
     "--strict-config",
     "--verbose",
     "--tb=short",
+    "--maxfail=3",
+    "-ra",
+    "--durations=10",
 ]
+
+# Test markers
 markers = [
-    "slow: marks tests as slow (deselect with '-m \"not slow\"')",
-    "integration: marks tests as integration tests",
-    "unit: marks tests as unit tests",
+    # Test speed
+    "slow: marks tests as slow (use -m 'not slow' to skip)",
+    "addon_disruptive: restarts the server-under-test's own process (addon self-restart); must never run concurrently with other tests on lanes where the MCP server is out-of-process - the lane workflow runs these in a single-worker phase AFTER the parallel run",
+
+    # Test types
+    "unit: unit tests (isolated, fast)",
+    "integration: integration tests requiring external services",
+    "e2e: end-to-end tests with full system",
+    "performance: performance and load tests",
+
+    # E2E test categories
     "automation: automation lifecycle tests",
+    "blueprint: blueprint management tests",
     "calendar: calendar event management tests",
     "device: device control tests",
     "script: script orchestration tests",
     "helper: helper integration tests",
+    "integrations: integration management tests (config entries)",
+    "labels: label management tests",
+    "registry: entity and device registry tests",
+    "services: service discovery tests",
+    "todo: todo/shopping list management tests",
     "convenience: convenience tools tests (scene, weather, energy, docs)",
+    "updates: update management tools tests",
+    "system: system management tests (restart, reload, health)",
+    "themes: frontend theme management tests",
     "error_handling: error handling and edge case tests",
     "cleanup: tests that create entities needing cleanup",
-    "performance: performance measurement and regression tests",
-    "external_only: in-process-server tiers only; skips inaddon, stdio, container-embedded, and HAOS-embedded servers",
-    "inaddon_only: only runs on HAOS inaddon tier",
+    "area: area management tests",
+    "floor: floor management tests",
+    "zone: zone management tests",
+    "group: entity group management tests",
+    "hacs: HACS (Home Assistant Community Store) tests",
+    "update_path: component (stable tag + working tree) x new-server in-process update-path e2e (dedicated lane; runs only with E2E_UPDATE_PATH=1; #1783/#1785)",
+    "core: core tool tests (state, service, bulk control, history, templates)",
+    "config: configuration management tests (helpers, labels)",
+    "filesystem: filesystem access tools tests",
+    "haos_only: skip unless HAOS_TEST_IMAGE_PATH is set (HAOS-QEMU backend required; #1281)",
     "beta_haos_only: beta HAOS image lanes with Supervisor/Core version expectations configured",
+    "container_only: skip when HAOS backend is active (testcontainer-specific behavior; #1281)",
+    "embedded_only: only the embedded testcontainer backend (E2E_BACKEND=embedded), the one lane that installs ha-mcp into the HA image (#2245)",
+    "external_only: in-process-server tiers only - skip for inaddon, stdio, container-embedded, and HAOS-embedded servers; #1349, #1527, #2233",
+    "inaddon_only: HAOS inaddon mode only - exercises is_running_in_addon()=True paths; #1349",
+    "haos_stdio_only: HAOS stdio mode only - exercises the installed ha-mcp command over a real stdio subprocess transport; #2233",
+    "haos_tls: final HAOS embedded scenario that restarts Core with HTTPS in the existing worker VM, then restores HTTP; #2241",
+    "haos_embedded_only: HAOS embedded mode only (HAOS_TEST_MODE=embedded) - the server shares Home Assistant's process and event loop; #2357",
+    "not_on_embedded: skip on the embedded backend (E2E_BACKEND=embedded) - provably redundant with the lane's own in-process ha_mcp_server session backend; #1527",
+    "not_on_haos_embedded: skip on the haos_embedded backend (HAOS_TEST_MODE=embedded) - provably redundant with the lane's own session backend, which enables the entry once and drives the in-process server for the whole suite; #1527",
+    "requires_tools_entry: needs the File & YAML Tools config entry - skipped on E2E_NO_TOOLS_ENTRY=1 lanes (#2292)",
+    "no_tools_only: runs only on E2E_NO_TOOLS_ENTRY=1 lanes (#2292)",
 ]
+
+# Async support - session-scoped loop lets session-scoped fixtures
+# (mcp_server, mcp_client, ha_client) share one event loop with tests.
+# Without this, each test gets a new loop and session-scoped httpx
+# clients fail with "Event loop is closed".
 asyncio_mode = "auto"
+asyncio_default_fixture_loop_scope = "session"
+asyncio_default_test_loop_scope = "session"
+
+# Per-test timeout (pytest-timeout). A stuck server-side await otherwise
+# stalls the run silently until the JOB timeout - observed as a 22-minute
+# hang in test_zone_search_discovery on the HAOS in-addon backend. 300s is
+# ~10x the slowest legitimate test (~30s deliberate-timeout tests). The signal
+# method interrupts only the hung test and raises inside the running coroutine,
+# so the failure traceback names the exact stuck await.
+timeout = 300
+timeout_method = "signal"
+# Bill the timeout to the TEST FUNCTION only. Session fixtures (container
+# boot, the embedded backend's server bring-up, HAOS staging) legitimately
+# exceed 300s and were being killed mid-setup on the first test per worker,
+# preempting their own diagnostics. Runaway fixtures are still bounded by
+# the CI job timeouts.
+timeout_func_only = true
+
+# Log capture
+log_cli = true
+log_cli_level = "INFO"
+log_cli_format = "%(asctime)s [%(levelname)8s] %(name)s: %(message)s"
+log_cli_date_format = "%Y-%m-%d %H:%M:%S"
+
+# Treat warnings as errors to enforce clean tests
+filterwarnings = [
+    "error",
+    # Allow specific non-critical warnings that don't affect functionality
+    "ignore::DeprecationWarning",
+    "ignore::PendingDeprecationWarning",
+    # Allow all ResourceWarnings, including those emitted during test cleanup
+    "ignore::ResourceWarning",
+]
 
 [dependency-groups]
 dev = [

{ha_mcp_dev-8.4.3.dev2648 → ha_mcp_dev-8.4.3.dev2650/src/ha_mcp_dev.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 8.4.3.dev2648
+Version: 8.4.3.dev2650
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT