mirror of
https://github.com/Sea-Haven-Industries/procurement-ingest.git
synced 2026-09-30 07:13:13 +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.
166 lines
5.6 KiB
Python
166 lines
5.6 KiB
Python
"""Tests for the sticky-Cancelled merge semantics in the PO email processor.
|
|
|
|
These exercise the atomic conditional write in ``_merge_update`` that makes
|
|
"Cancelled" a sticky, authoritative status: once a PO is Cancelled, a later
|
|
new_po or revision may enrich its other fields but can never move it back to a
|
|
non-cancelled status. The invariant is enforced server-side with a DynamoDB
|
|
ConditionExpression, so it holds even under concurrent email processing — there
|
|
is no read-then-write TOCTOU window.
|
|
|
|
A real in-memory purchase-orders table is stood up with moto so the tests
|
|
exercise the actual DynamoDB conditional-write and ConditionalCheckFailedException
|
|
fallback path, not a stub.
|
|
"""
|
|
|
|
import boto3
|
|
import pytest
|
|
from moto import mock_aws
|
|
|
|
|
|
@pytest.fixture
|
|
def po_table(po_persistence):
|
|
"""Stand up a mock purchase-orders table matching the real key schema.
|
|
|
|
Phase 5 moved PO_TABLE onto persistence.py; key the mock table on
|
|
``po_persistence.PO_TABLE`` so the fixture and the save_* code under test
|
|
resolve the same name from one source rather than a duplicated literal.
|
|
"""
|
|
with mock_aws():
|
|
resource = boto3.resource("dynamodb", region_name="us-east-1")
|
|
table = resource.create_table(
|
|
TableName=po_persistence.PO_TABLE,
|
|
KeySchema=[{"AttributeName": "po_number", "KeyType": "HASH"}],
|
|
AttributeDefinitions=[
|
|
{"AttributeName": "po_number", "AttributeType": "S"},
|
|
],
|
|
BillingMode="PAY_PER_REQUEST",
|
|
)
|
|
table.wait_until_exists()
|
|
yield table
|
|
|
|
|
|
def _item(table, po_number):
|
|
return table.get_item(Key={"po_number": po_number}).get("Item")
|
|
|
|
|
|
def test_revision_cannot_uncancel_but_enriches(po_handler, po_table):
|
|
"""(a) Revision carrying a live status onto a Cancelled PO keeps it Cancelled
|
|
while still writing the other revision fields (no resurrection)."""
|
|
po_table.put_item(
|
|
Item={
|
|
"po_number": "PO-A",
|
|
"po_status": "Cancelled",
|
|
"cancelled_at": "2026-07-01T00:00:00",
|
|
}
|
|
)
|
|
|
|
po_handler.save_revision(
|
|
{
|
|
"po_number": "PO-A",
|
|
"po_status": "Issued",
|
|
"total_amount": 500,
|
|
"supplier": {"name": "Acme"},
|
|
}
|
|
)
|
|
|
|
item = _item(po_table, "PO-A")
|
|
assert item["po_status"] == "Cancelled" # not resurrected
|
|
assert item["cancelled_at"] == "2026-07-01T00:00:00" # marker preserved
|
|
assert item["total_amount"] == 500 # other fields still enriched
|
|
assert item["supplier"] == {"name": "Acme"}
|
|
|
|
|
|
def test_revision_without_status_merges_on_cancelled(po_handler, po_table):
|
|
"""(b) Revision with NO po_status onto a Cancelled PO merges cleanly, no
|
|
exception, status stays Cancelled."""
|
|
po_table.put_item(Item={"po_number": "PO-B", "po_status": "Cancelled"})
|
|
|
|
po_handler.save_revision({"po_number": "PO-B", "total_amount": 250})
|
|
|
|
item = _item(po_table, "PO-B")
|
|
assert item["po_status"] == "Cancelled"
|
|
assert item["total_amount"] == 250
|
|
|
|
|
|
def test_revision_updates_status_on_non_cancelled(po_handler, po_table):
|
|
"""(c) Issue B: a legitimate status update on a NON-cancelled PO is applied,
|
|
never dropped."""
|
|
po_table.put_item(Item={"po_number": "PO-C", "po_status": "Issued"})
|
|
|
|
po_handler.save_revision(
|
|
{"po_number": "PO-C", "po_status": "Revised", "total_amount": 999}
|
|
)
|
|
|
|
item = _item(po_table, "PO-C")
|
|
assert item["po_status"] == "Revised"
|
|
assert item["total_amount"] == 999
|
|
|
|
|
|
def test_new_po_backfills_cancelled_skeleton(po_handler, po_table):
|
|
"""(d) new_po onto a Cancelled skeleton backfills its fields but keeps the
|
|
Cancelled status and cancellation marker."""
|
|
po_table.put_item(
|
|
Item={
|
|
"po_number": "PO-D",
|
|
"po_status": "Cancelled",
|
|
"cancelled_at": "2026-07-02T00:00:00",
|
|
}
|
|
)
|
|
|
|
po_handler.save_new_po(
|
|
{
|
|
"po_number": "PO-D",
|
|
"po_status": "Issued",
|
|
"supplier": {"name": "Beta"},
|
|
"total_amount": 1200,
|
|
}
|
|
)
|
|
|
|
item = _item(po_table, "PO-D")
|
|
assert item["po_status"] == "Cancelled"
|
|
assert item["cancelled_at"] == "2026-07-02T00:00:00"
|
|
assert item["supplier"] == {"name": "Beta"}
|
|
assert item["total_amount"] == 1200
|
|
|
|
|
|
def test_new_po_creates_fresh(po_handler, po_table):
|
|
"""(e) new_po on a fresh PO creates it normally with its status."""
|
|
po_handler.save_new_po(
|
|
{"po_number": "PO-E", "po_status": "Issued", "total_amount": 42}
|
|
)
|
|
|
|
item = _item(po_table, "PO-E")
|
|
assert item["po_status"] == "Issued"
|
|
assert item["total_amount"] == 42
|
|
|
|
|
|
def test_revision_creates_fresh_merge(po_handler, po_table):
|
|
"""(e) revision on a fresh PO merges/creates normally with its status."""
|
|
po_handler.save_revision(
|
|
{"po_number": "PO-F", "po_status": "Revised", "total_amount": 77}
|
|
)
|
|
|
|
item = _item(po_table, "PO-F")
|
|
assert item["po_status"] == "Revised"
|
|
assert item["total_amount"] == 77
|
|
|
|
|
|
def test_save_cancellation_is_authoritative(po_handler, po_table):
|
|
"""Cancellation always wins: save_cancellation writes Cancelled over a live
|
|
status while leaving previously-established data intact."""
|
|
po_table.put_item(
|
|
Item={"po_number": "PO-G", "po_status": "Issued", "total_amount": 300}
|
|
)
|
|
|
|
po_handler.save_cancellation(
|
|
{
|
|
"po_number": "PO-G",
|
|
"processed_at": "2026-07-03T00:00:00",
|
|
"raw_s3_key": "s3://bucket/key",
|
|
}
|
|
)
|
|
|
|
item = _item(po_table, "PO-G")
|
|
assert item["po_status"] == "Cancelled"
|
|
assert item["cancelled_at"] == "2026-07-03T00:00:00"
|
|
assert item["total_amount"] == 300 # pre-existing data retained
|