The table separates scenarios with test bindings from proposed proof. A binding records a static examination of the test; it does not record a passing product test run.
Workspace sessions differ in application availability and readable destinations; the registry includes applications with built destinations and applications with only planned destinations.
Steps
Render each session, including both applications visible, CRM omitted and Accounting omitted, and compare the displayed registry-backed sections with the eligible registry entries.
Expected
Each displayed sequence matches the eligible subsequence of the registry; the assertion allows different visible application sets and checks adjacency whenever both named sections survive.
Data
Sessions covering both applications, each separately omitted, and differing build eligibility; existing permission and build policies supply the visibility inputs.