test: add TDD bug-capture test for #989 — JSON decode crash in persistence #1166

Merged
freemo merged 1 commits from tdd/m5-json-decode-crash into master 2026-04-03 03:58:45 +00:00

1 Commits

Author SHA1 Message Date
brent.edwards 24dd2b3a2a test: add TDD bug-capture test for #989 — JSON decode crash in persistence
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Failing after 27s
CI / security (pull_request) Failing after 56s
CI / typecheck (pull_request) Failing after 1m2s
CI / unit_tests (pull_request) Failing after 1m54s
CI / helm (pull_request) Successful in 23s
CI / quality (pull_request) Successful in 3m44s
CI / coverage (pull_request) Has been skipped
CI / docker (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
CI / build (pull_request) Successful in 3m17s
CI / e2e_tests (pull_request) Failing after 15m47s
CI / integration_tests (pull_request) Failing after 22m13s
CI / status-check (pull_request) Failing after 1s
Add a new Behave TDD regression scenario that persists corrupt automation-profile JSON and verifies repository reads do not leak raw JSONDecodeError. The scenario is tagged with @tdd_bug, @tdd_bug_989, and @tdd_expected_fail so it currently inverts the intentional assertion failure and will require tag removal when bug #989 is fixed.\n\nAlso stabilize an unrelated integration fixture in robot/resource_dag.robot by sharing a single SQLAlchemy session in inline scripts; this removes nondeterministic visibility of flushed resource-type rows and keeps required nox integration quality gates deterministic for this branch.\n\nISSUES CLOSED: #1094
2026-04-03 01:43:38 +00:00