The "Category Code" field had no TableRelation at all, so the good
subscriber's RemoveTableRelation call targeted metadata that never
existed - a no-op. Added a real TableRelation to "Sample Setup" on
that field (the one known exception to exclude) and a second,
ordinary self-referencing relation ("Parent No." -> "Sample
Header"."No.") with no exception. The good fixture now removes only
the first; the bad fixture's table-wide removal (field/related
table/field all 0) now demonstrably also strips the second, showing
the actual anti-pattern instead of removing nothing meaningful.
- al-testing-review.md: the generic ExpectedError cue's asserterror
Assert.IsTrue/IsFalse exclusion was unconditional, but the
specialized rule it deferred to only claims the pure-inversion
shape. A test expecting the guarded Boolean-returning call itself to
raise fell through both routes. Narrowed the exclusion to the same
inversion-only condition the specialized cue already uses.
- asserterror-needs-expectederror-and-code.md: the rollback-sentinel
exception (a trailing asserterror Error(...) used purely to force a
fixture rollback, not to verify a specific failure) previously lived
only in skill routing prose. Encoded it directly in the article's
Anti Pattern section so every consumer of the knowledge base sees it,
not just this one skill.
- commit-shared-test-fixture-inside-lazy-initialize.good.al/.bad.al:
replaced hand-rolled Item.Init()/Insert(true) with
LibraryInventory.CreateItem, so the canonical fixture doesn't itself
trigger use-library-codeunits-for-test-fixtures.
- table-relation-test-exclude-known-invalid-relations-via-event.good.al/
.bad.al: declared minimal "Sample Setup"/"Sample Header" tables
inline instead of referencing undefined symbols, matching this
repo's own convention that every fixture is self-contained.
Fourth batch from CURABIS ApS, mined from an external BC/NAV testing expert's blog archive (fluxxus.nl). Confirm+StrSubstNo interaction with ConfirmHandler, Table Relation Test's OnAfterRemoveTableRelation exclusion hook (verified against BCApps source, codeunit 134926), committing shared lazy-Initialize fixture data, and Assert.IsFalse vs asserterror for boolean checks.
