Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-06 23:26:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/testing/use-testpage-visible-enabled-to-verify-field-ui-state.md
Michael Dieringer 1028aacd4f Add 3 more AL/BC patterns from CURABIS Academy testing course material 
Third batch from CURABIS ApS: item-ledger-entry document-no lookup after Ship-and-Invoice posting, TestPage.Visible()/.Enabled() as the mechanism for verifying field UI state, and LibraryUtility.GenerateGUID() for collision-free test fixture values.
2026-09-21 22:34:40 +02:00

1.2 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
testing
testpage
visible
enabled
ui-state
headless-test
field-verification
al
w1
all

Verify field visibility and editability with TestPage.Visible()/.Enabled()

Description

A UI test codeunit does not need to inspect table or page properties indirectly to confirm a field is shown or editable under given conditions. The TestPage object exposes a Visible() and an Enabled() function on each field, reflecting the page's actual rendered state, callable directly from a [Test] procedure after OpenView().

Best Practice

Open the TestPage, navigate to the relevant record if needed, then assert against TestPageField.Visible() and TestPageField.Enabled() to verify the field's UI state, rather than checking an unrelated table/page property or skipping the check.

See sample: use-testpage-visible-enabled-to-verify-field-ui-state.good.al.

Anti Pattern

A test that opens the TestPage but never asserts against Visible()/Enabled() on the field in question — confirming only that the page opens, not that the field behaves as expected.

See sample: use-testpage-visible-enabled-to-verify-field-ui-state.bad.al.