mirror of
https://github.com/Sea-Haven-Industries/procurement-ingest.git
synced 2026-09-30 06:03:14 +00:00
* test: consolidate test roots — one repo-root loader, shared support package, missing-scenario suites, enforced ruff/coverage floor (refactor phase 8) tests/conftest.py only loads for the tests/ root, not a standalone `pytest lambdas/po/email_processor/tests` run, so it could never carry session invariants like the dummy AWS env or the moto stubber registration. Add a single repo-root conftest.py (pytest.ini pins rootdir there, so it loads for every invocation) that sets the dummy AWS credentials/region, imports moto BEFORE any handler module so boto3 sessions pick up its stubber hook (carrying the explanatory comment verbatim from the old _po_parser_support.py), and exposes one load_lambda_module(pipeline, name) — the sys.modules save/restore dance stays, since template_parser is still a duplicated bare name across pipelines needing per-exec sibling binding. Add tests/support/ as the shared package both pipelines' local _*_parser_support.py modules delegate to: a superset FakeTable (PO's update_item recording + WO's put_item and keyed single-row store), FakeDynamoResource, load_email, and load_golden with parse_float=Decimal kept (load-bearing for exact money comparison at PO magnitudes — WO's prior load_golden had no parse_float and must not regress PO by losing it). Rewrite _wo_parser_support.py off the bare `import handler` / `from handler import parse_raw_email` strategy that was the source of the bare-name sys.modules collision the other two loaders defend against. Move test_po_merge.py and test_pad_zip.py into lambdas/po/email_processor/tests/ (PO-specific, belongs beside the code) via git mv so history follows; test_parse_raw_email.py and test_ses_auth.py stay at the repo root since they're genuinely cross-pipeline, parameterized over both handlers. Delete tests/test_local.py: it globs a nonexistent samples/ dir, is WO-only, and imports a handler at collection time, bypassing the loader gate entirely — the golden suites already cover its role. Its pytest.ini exclusion comment goes with it. New scenario coverage, all built on the single loader + support package: - PO+WO Bedrock transport errors (ThrottlingException, missing 'content' key, empty content list, non-JSON model text), asserting PO's pre-call ai_fallback metric survives with no partial write and the exception propagates; WO's no-datapoint-on-throttle behavior is pinned with a documenting test rather than "fixed" by reordering. - Handler-level SES-auth reject seam per pipeline: no auth monkeypatch + empty ALLOWED_DKIM_DOMAINS asserts zero Bedrock calls, zero writes, no raise — closing the hole where deleting the gate line today still passes every test. - web_ui coverage for both PO and WO (0% before this): fail-closed on unset ARN and on a Secrets Manager exception, TTL cache refresh, Bearer/X-Auth-Token/header-case-insensitivity, wrong-token 401 with no table scan, non-ASCII token, and a hostile-field-escaping regression lock. PO web_ui has no __init__.py, so these go through the loader rather than package imports. - A moto-backed mirror of test_po_merge for WO merge semantics (table 'WorkOrders'): null-status never clobbers wo_status, created_at immutable via if_not_exists, status->wo_status mapping, None fields absent from SET, record_type only-when-present. - Small pins: the PO-DC-02 64-char EMF clamp regression and per-pipeline multi-record failure-isolation (all-or-retry contract). The reprocess.py synthetic-event-shape contract test already landed in Phase 7, so it isn't duplicated here. Two WO product-code fixes ride along, since this is the phase that exercises them: (a) the invalid_status reason-code fix in template_parser.py's status check, which previously returned malformed_site_code for the same failure validate_ai_fallback already labels invalid_status, making one failure surface two codes depending on path (grepped the dashboards/metric filters for malformed_site_code first — no external references found, safe to diverge the two codes); (b) wrapping the WO Bedrock call in handler.py so a transport failure emits ai_fallback/bedrock_error in an except-and-reraise. This is deliberately not a naive reorder: the emit sits in the except block, not pre-call, so a gate-rejected email still emits only ai_fallback_rejected and wo_stack's "a rejected email emits nothing else" alarm contract doesn't double-count. A test computes the emitted series by hand to pin the no-double-count behavior. Neither change touches the handler event/return contract. _validate_new_po_values in the PO template_parser.py is split into per-rule helpers, and the V4 anchor-frame dataclass now carries summary_matches/price so V13 can consume them; extract_new_po (C901=35) is included in the split. Add ruff.toml enabling C901/PLR so the mccabe/complexity suppressions scattered through the tree stop being decorative; derived_fields.py is under the shadow-bake freeze so its violations are silenced via a per-file ignore with a justification comment instead of an in-file edit, and the handful of other pre-existing violations surfaced by turning the config on get the same per-file-ignore treatment with a reason, or a fix where the file isn't frozen. scripts/ is added to the CI lint scope. CI gains an explicit --cov module list (lambdas/po and wo email_processor + web_ui, po/site_extractor, lambdas/shared) plus --cov-fail-under=80, since web_ui and site_extractor lack __init__.py markers and a bare --cov=lambdas silently skips them for the missing package marker; .coveragerc omits the test dirs themselves from the count. The Phase 0 AST bundle-consistency test stays in the standard pytest run. .gitignore picks up the resulting .coverage data file. docs/po-template-parser.md gets a small correction: the EXTRACTION_PROMPT declares quantity/price as "number or null", not JSON strings, so parse_float=Decimal already handles a conforming Bedrock response — the doc previously implied the coercion path was the primary mechanism rather than a defensive net for non-conforming responses. * test: lock attribute-context quote escaping in web_ui hostile-field test The escaping regression lock asserted only the element-context vector (raw <script> absent, <script> present) while its docstring claimed quotes were covered -- the payload's " and ' were never asserted on, so a quote-escaping regression on the onclick row-link sink (attribute breakout -> event-handler injection) would have passed green. /sh-security-review finding WC-01 (confirmed medium, test-integrity). Add assertions that the onclick sink's JSON string renders its opening quote as " (raw " after window.location= fails), that the payload's quote characters appear only entity-escaped, and that the raw payload never appears anywhere in the body. Mutation-verified: the test now fails when the sink's quote-escaping is dropped. * test: address Open SWE review — xfail the web_ui non-ASCII auth pin, document subset coverage-floor override - tests/test_web_ui_auth.py: replace the TypeError characterization pin with an xfail(strict, raises=TypeError) asserting the DESIRED fail-closed (False) behavior. Documents the intended fix and auto-fails (xpass) once web_ui_auth is corrected, instead of requiring a passing test to be knowingly deleted. The module stays frozen this phase; the underlying hmac.compare_digest ASCII-only defect is tracked as a follow-up. - pytest.ini: document that the aggregate 80% floor (enforced in CI via the reusable workflow's bare pytest) red-exits local subset runs by design, with the --cov-fail-under=0 override for iteration. Floor stays in addopts because the centralized ci-python-sam workflow exposes no per-run test command.
123 lines
4.8 KiB
Python
123 lines
4.8 KiB
Python
"""Moto-backed merge-semantics tests for save_work_order (constraint 5d).
|
|
|
|
A real in-memory work-orders table is stood up with moto so these exercise the
|
|
actual DynamoDB UpdateExpression build -- the reserved-word status->wo_status
|
|
mapping, the if_not_exists created_at guard, and the None-field-dropping logic --
|
|
against a real store rather than a stub. Mirrors tests/test_po_merge.py's
|
|
approach, placed beside the WO code (same constraint-3 principle that moved
|
|
test_po_merge out of the repo-root tests/).
|
|
|
|
The table name comes from ``wo_persistence.WORK_ORDERS_TABLE`` (default the
|
|
literal ``"WorkOrders"``, NOT a kebab-case name) so the fixture and the code
|
|
under test resolve the same name from one source. persistence.py is untouched --
|
|
this is a pure new-test addition pinning four existing-but-untested behaviors.
|
|
"""
|
|
|
|
import boto3
|
|
import pytest
|
|
from moto import mock_aws
|
|
|
|
|
|
@pytest.fixture
|
|
def wo_table(wo_persistence):
|
|
with mock_aws():
|
|
resource = boto3.resource("dynamodb", region_name="us-east-1")
|
|
table = resource.create_table(
|
|
TableName=wo_persistence.WORK_ORDERS_TABLE,
|
|
KeySchema=[{"AttributeName": "work_order_id", "KeyType": "HASH"}],
|
|
AttributeDefinitions=[
|
|
{"AttributeName": "work_order_id", "AttributeType": "S"},
|
|
],
|
|
BillingMode="PAY_PER_REQUEST",
|
|
)
|
|
table.wait_until_exists()
|
|
# Point the lazily-cached module resource at the moto-mocked one.
|
|
wo_persistence.dynamodb = resource
|
|
try:
|
|
yield table
|
|
finally:
|
|
wo_persistence.dynamodb = None
|
|
|
|
|
|
def _item(table, work_order_id):
|
|
return table.get_item(Key={"work_order_id": work_order_id}).get("Item")
|
|
|
|
|
|
def _parsed(work_order_id, **overrides):
|
|
base = {
|
|
"work_order_id": work_order_id,
|
|
"email_type": "update",
|
|
"description": None,
|
|
"status": None,
|
|
"site_code": None,
|
|
"building": None,
|
|
"address": None,
|
|
"severity": None,
|
|
"priority": None,
|
|
"date_reported": None,
|
|
"scheduled_start": None,
|
|
"due_date": None,
|
|
"assigned_to": None,
|
|
}
|
|
base.update(overrides)
|
|
return base
|
|
|
|
|
|
def test_null_status_never_clobbers_wo_status(wo_persistence, wo_table):
|
|
"""A later email with status=None must NOT overwrite an established
|
|
wo_status (None fields are dropped from the SET clause)."""
|
|
wo_table.put_item(Item={"work_order_id": "WO-A", "wo_status": "assigned"})
|
|
|
|
wo_persistence.save_work_order(_parsed("WO-A", status=None), "s3://b/k")
|
|
|
|
item = _item(wo_table, "WO-A")
|
|
assert item["wo_status"] == "assigned" # not clobbered
|
|
|
|
|
|
def test_created_at_immutable_via_if_not_exists(wo_persistence, wo_table):
|
|
"""created_at is set with if_not_exists, so the first write's value survives
|
|
every subsequent upsert."""
|
|
wo_persistence.save_work_order(_parsed("WO-B"), "s3://b/k1")
|
|
first = _item(wo_table, "WO-B")["created_at"]
|
|
|
|
wo_persistence.save_work_order(_parsed("WO-B", description="later"), "s3://b/k2")
|
|
second = _item(wo_table, "WO-B")
|
|
|
|
assert second["created_at"] == first # immutable
|
|
assert second["description"] == "later" # other fields still enriched
|
|
assert second["updated_at"] >= first # updated_at is always refreshed
|
|
|
|
|
|
def test_status_maps_to_wo_status_reserved_word(wo_persistence, wo_table):
|
|
"""'status' is a DynamoDB reserved word -- the source field maps to the
|
|
'wo_status' attribute, and no attribute literally named 'status' is written."""
|
|
wo_persistence.save_work_order(_parsed("WO-C", status="completed"), "s3://b/k")
|
|
|
|
item = _item(wo_table, "WO-C")
|
|
assert item["wo_status"] == "completed"
|
|
assert "status" not in item
|
|
|
|
|
|
def test_none_fields_absent_from_set_clause(wo_persistence, wo_table):
|
|
"""None source fields are dropped from the SET clause: a pre-existing
|
|
attribute is retained rather than being overwritten with None."""
|
|
wo_table.put_item(
|
|
Item={"work_order_id": "WO-D", "building": "B12", "priority": "high"}
|
|
)
|
|
|
|
wo_persistence.save_work_order(_parsed("WO-D", description="fix door"), "s3://b/k")
|
|
|
|
item = _item(wo_table, "WO-D")
|
|
assert item["description"] == "fix door" # the one non-None field written
|
|
assert item["building"] == "B12" # pre-existing attrs retained
|
|
assert item["priority"] == "high"
|
|
|
|
|
|
def test_record_type_only_when_email_type_present(wo_persistence, wo_table):
|
|
"""record_type is written only when email_type is present (truthy); a falsy
|
|
email_type leaves the attribute absent."""
|
|
wo_persistence.save_work_order(_parsed("WO-E", email_type="new_work_order"), "s")
|
|
assert _item(wo_table, "WO-E")["record_type"] == "new_work_order"
|
|
|
|
wo_persistence.save_work_order(_parsed("WO-F", email_type=""), "s")
|
|
assert "record_type" not in _item(wo_table, "WO-F")
|