BC Observatoryunofficial, made by waldo
code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#62 Add testing knowledge: UI handlers, table relations, asserterror, fixtures (P1+P2)

Adds three testing knowledge articles to BCQuality under microsoft/knowledge/testing: UI handlers in tests, pairing asserterror with expected error checks, and using library codeunits for test fixtures. Each article has a markdown page plus good and bad AL examples.

Open in Claude62.mdPull request #62

Pull request · merged into main on 2026-07-09 by JesperSchulz · 9 files (+277 -0), 9 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • New article on UI handlers needed for UI calls in tests
  • New article on pairing asserterror with Assert.ExpectedError and ExpectedErrorCode
  • New article on using library codeunits instead of hand-rolled Init/Insert fixtures
  • Each article ships as a markdown file with good and bad AL samples
  • Content targets BC-specific test mechanics that LLMs tend to get wrong

AL objects touched

  • microsoft/knowledge/testing/asserterror-needs-expectederror-and-code.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/asserterror-needs-expectederror-and-code.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/asserterror-needs-expectederror-and-code.md: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/ui-handlers-in-tests.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/ui-handlers-in-tests.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/ui-handlers-in-tests.md: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/use-library-codeunits-for-test-fixtures.bad.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/use-library-codeunits-for-test-fixtures.good.al: added, not in the BC? snapshot yet
  • microsoft/knowledge/testing/use-library-codeunits-for-test-fixtures.md: added, not in the BC? snapshot yet

Context

  • Systems: development

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).