1.7.0-dev-SNAPSHOT

Runs

StatusBrowserStartedPassedFailed FlakySkippedCommitLinks
passed msedge 2026-11-10 09:11 UTC 323 0 0 0 c3273742 Summary Full report Workflow run
failed msedge 2026-11-10 07:14 UTC 315 8 0 0 585e039c Summary Full report Workflow run
failed msedge 2026-11-09 14:13 UTC 273 14 0 17 6a72a620 Summary Full report Workflow run

Latest run msedge, 2026-11-10 09:11 UTC

Status
passed
Started
2026-11-10 09:11 UTC (34 min)
Tests
323: 323 passed, 0 failed, 0 flaky, 0 skipped
Tests from
feature/1.7.0-dev c3273742
Links
Full Playwright report Permalink of this run Workflow run (logs, traces)

Features

FeaturePassedFailedFlaky Skipped
administration172 000
batch-import24 000
comments25 000
dashboards19 000
data-eng48 000
portal27 000
superset8 000

Tests

administration

StatusTestJiraDuration
Disabled user
HELLODATA-4156: a user disabled in the portal can still log in (the Keycloak realms are shared), but gets no permissions at all and sees only the admins to contact
passed
sees only the list of admins to contact and no menu entries of its role
the disabled user logs in and gets no permissions: the page lists the admins to contact; there is no dashboards panel and no Data Marts menu entry
administration/disabled-user.spec.ts:64 all actions in the report
 HELLODATA-4156 2.4 s
passed
is sent back to the home page when it opens a page by url
the disabled user opens pages by url (data marts viewer, announcements); each time it is sent back to the home page with the missing permissions notice
administration/disabled-user.spec.ts:80 all actions in the report
 HELLODATA-4156 3.5 s
passed
gets its access back when the admin enables it again
the admin enables the user again; after the next login the user sees its dashboards panel and the Data Marts menu, and the missing permissions notice is gone
administration/disabled-user.spec.ts:91 all actions in the report
 HELLODATA-4156 9.6 s
FAQ management
the admin manages the FAQ entries of the portal
passed
admin creates, edits and deletes a FAQ
the admin creates a FAQ in the FAQ management, edits its text and deletes it; after each step the list and the FAQ content show the change
administration/faq.spec.ts:7 all actions in the report
 7.7 s
Page access by url › HELLODATA_ADMIN
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
opens embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
opens advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
opens users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.0 s
passed
opens subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.0 s
passed
opens bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
opens workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
opens documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
Page access by url › BUSINESS_DOMAIN_ADMIN
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
opens advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
opens dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.4 s
passed
opens dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.1 s
passed
opens users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
opens subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
is not allowed to open workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
opens embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
Page access by url › DATA_DOMAIN_ADMIN
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
Page access by url › DATA_DOMAIN_EDITOR
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
opens embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
is not allowed to open advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
is not allowed to open external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.0 s
passed
is not allowed to open dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
is not allowed to open dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
passed
is not allowed to open dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
is not allowed to open users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
is not allowed to open subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
Page access by url › DATA_DOMAIN_BUSINESS_SPECIALIST
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
opens embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 1.0 s
passed
is not allowed to open queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.9 s
Page access by url › DATA_DOMAIN_VIEWER
every role opens each page by its url; it is shown when the role has the permission, otherwise the user is sent to the forbidden page the pages opened by url with a user of this role
passed
opens published-announcements (DASHBOARDS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens external-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open embedded-dm-viewer (DATA_MARTS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open advanced-analytics-viewer/Default_Data_Domain (DATA_JUPYTER)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open external-dashboards/create (EXTERNAL_DASHBOARDS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open dashboard-access/list (DASHBOARD_ACCESS)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-groups/list/Default_Data_Domain (DASHBOARD_GROUPS_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
is not allowed to open dashboard-import-export (DASHBOARD_IMPORT_EXPORT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open users-overview (USERS_OVERVIEW)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open subsystem-users (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open bulk-assignments (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
is not allowed to open workspaces (WORKSPACES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open announcements-management (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open announcements-management/create (ANNOUNCEMENT_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open faq-management (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open faq-management/create (FAQ_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open documentation-management (DOCUMENTATION_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.7 s
passed
is not allowed to open roles-management (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.8 s
passed
is not allowed to open roles-management/create (ROLE_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open user-management (USER_MANAGEMENT)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.6 s
passed
is not allowed to open embedded-orchestration (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open embedded-orchestration-airflow3 (DATA_ENG)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
opens lineage-docs/list (DATA_LINEAGE)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.4 s
passed
opens my-dashboards (-)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
passed
is not allowed to open queries/list/Default_Data_Domain (QUERIES)
the user of this role opens the page by url; with the required permission the page is shown, without it the user lands on the forbidden page
administration/page-access.spec.ts:101 all actions in the report
 0.5 s
Roles › HELLODATA_ADMIN
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.4 s
passed
sees only the administration entries of its role
the user opens the Administration menu and sees exactly the entries allowed for its role
administration/roles.spec.ts:82 all actions in the report
 2.6 s
Roles › BUSINESS_DOMAIN_ADMIN
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.6 s
passed
sees only the administration entries of its role
the user opens the Administration menu and sees exactly the entries allowed for its role
administration/roles.spec.ts:82 all actions in the report
 3.5 s
Roles › DATA_DOMAIN_ADMIN
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.9 s
passed
sees only the administration entries of its role
the user opens the Administration menu and sees exactly the entries allowed for its role
administration/roles.spec.ts:82 all actions in the report
 6.6 s
passed
is not allowed to open user management by url
the user opens the user management by url and is sent to the forbidden page without seeing the users heading
administration/roles.spec.ts:93 all actions in the report
 3.5 s
Roles › DATA_DOMAIN_EDITOR
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.6 s
passed
is not allowed to open user management by url
the user opens the user management by url and is sent to the forbidden page without seeing the users heading
administration/roles.spec.ts:93 all actions in the report
 3.6 s
Roles › DATA_DOMAIN_BUSINESS_SPECIALIST
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.7 s
passed
is not allowed to open user management by url
the user opens the user management by url and is sent to the forbidden page without seeing the users heading
administration/roles.spec.ts:93 all actions in the report
 3.8 s
Roles › DATA_DOMAIN_VIEWER
which menu entries and pages each portal role can see a user of this role after logging in
passed
sees only the main menu entries of its role
the user sees exactly the main menu entries of its role in the sidebar and none of the others
administration/roles.spec.ts:72 all actions in the report
 2.4 s
passed
is not allowed to open user management by url
the user opens the user management by url and is sent to the forbidden page without seeing the users heading
administration/roles.spec.ts:93 all actions in the report
 3.1 s
User lifecycle
An admin invites a user, gives it a role in a data domain and deletes it again, all in the user management. The compose installation looks users up locally (LocalUserLookupProvider), so any email can be invited.
passed
admin invites a new user
the admin invites a new user by email in the user management; the portal opens the edit page of the user, who is created as enabled and not a superuser
administration/user-lifecycle.spec.ts:21 all actions in the report
 6.1 s
passed
admin gives the user a role in the data domain
the admin edits the invited user and gives it the data domain editor role; the role is stored in the portal and Superset has the BI_EDITOR and sql_lab roles for the user
administration/user-lifecycle.spec.ts:38 all actions in the report
 5.6 s
passed
admin deletes the user
the admin deletes the user in the user management and confirms; the user is gone from the list and the portal
administration/user-lifecycle.spec.ts:54 all actions in the report
 7.3 s
Users and roles
the profile of the logged in user and the user list of the admin the menus and pages each role may open are covered by roles.spec.ts
passed
profile shows the roles of the logged in user
the admin opens the profile from the user menu; it shows the admin's email and the HELLODATA ADMIN role
administration/users.spec.ts:7 all actions in the report
 3.5 s
passed
user management lists the admin and the example users
the admin opens the user management; the admin and the example users of the other roles are listed
administration/users.spec.ts:17 all actions in the report
 3.5 s

batch-import

StatusTestJiraDuration
Batch import - dashboard groups
HELLODATA-2073 / HELLODATA-2074: the dashboardGroup column puts viewers and business specialists into dashboard groups. Like the roles, the groups of a data domain are the ones of the file: a group that is no longer listed is left.
passed
adds a viewer to the groups of the file and removes it from groups no longer listed
an admin-imported viewer is put into the dashboard group named in the file; a second import without the group removes the viewer from that group again and the viewer keeps only the BI_VIEWER and RLS Superset roles
batch-import/dashboard-groups.spec.ts:41 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 8.0 s
Batch import - existing users
HELLODATA-2073 / HELLODATA-2074: users that already exist are changed to match the csv file. Roles that are not in the file are removed, in the portal and in Superset. Each test continues with the user the previous one left.
passed
replaces the RLS roles of a viewer with the ones of the file
a second import for an existing viewer lists another RLS role; the viewer ends up with the new RLS role only, the dashboard role stays and the showcase dashboard is still assigned in the portal
batch-import/existing-users.spec.ts:43 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 4.8 s
passed
removes roles that were given in Superset directly and dashboards that are no longer in the file
an RLS role added directly in Superset and the dashboard role missing in the next file are both removed; the viewer keeps only the RLS role of the file and has no portal dashboards left
batch-import/existing-users.spec.ts:53 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 5.4 s
passed
changes the data domain role and drops the roles only a viewer has
the file turns the viewer into a data domain editor; the portal role changes and in Superset the user gets BI_EDITOR and sql_lab instead of the viewer roles
batch-import/existing-users.spec.ts:66 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 4.9 s
passed
takes all access to the data domain away with the role NONE
the role NONE takes all data domain access away; the user stays enabled in the portal and has only BI_NO_ACCESS in Superset
batch-import/existing-users.spec.ts:76 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 4.9 s
passed
promotes a user to HelloDATA admin and back
a file makes the user HelloDATA admin (superuser, Admin and BI_ADMIN roles in Superset); a following file makes the user a plain viewer again and the superuser flag and the admin roles are gone
batch-import/existing-users.spec.ts:87 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 10.0 s
Batch import - file validation
HELLODATA-2075: the whole file is checked before any user is touched. A file with an error is rejected as a whole, the error is written to users-output.log and the file is left in the folder.
passed
rejects a file with an unknown data domain
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.5 s
passed
rejects a file with a Superset role that does not exist in Superset
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.7 s
passed
rejects a file with a dashboard group that does not exist
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.7 s
passed
rejects a file with an invalid email
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.5 s
passed
rejects a file with an unknown business domain role
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.5 s
passed
rejects a file with an unknown data domain role
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 6.6 s
passed
rejects a file with an empty data domain role
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.5 s
passed
rejects a file with columns separated by commas instead of semicolons
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.6 s
passed
rejects a file with only a header
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 4.6 s
passed
rejects a file with a dashboard group without the dashboardGroup column in the header
a file with this kind of error (see the test title) is rejected: the error is written to the import log and no user is created in the portal
batch-import/file-validation.spec.ts:94 all actions in the report
 HELLODATA-2075 6.6 s
passed
rejects the whole file when one of its rows is invalid
a file with one valid and one invalid row is rejected as a whole: the error of the invalid row is logged and neither of the two users is created
batch-import/file-validation.spec.ts:105 all actions in the report
 HELLODATA-2075 4.6 s
passed
accepts a file in the old format without the dashboardGroup column
a file with the old header without the dashboardGroup column is still accepted; the user gets the viewer role in the portal and the BI_VIEWER and RLS roles in Superset
batch-import/file-validation.spec.ts:119 all actions in the report
 HELLODATA-2075 6.8 s
Batch import - last record wins
HELLODATA-2073 / HELLODATA-2074: the rows are processed from top to bottom, so when a file has several rows for the same user, the end result is the one of its last row. The current state of an existing user counts like a row above the first one of the file.
passed
keeps the data domain and Superset roles of the last row of a new user
a new user with three rows in the file ends up with the data domain role and the Superset roles of the last row only; no dashboards are assigned
batch-import/last-record-wins.spec.ts:41 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 2.9 s
passed
keeps the business domain role of the last row
a user with an admin row followed by an editor row is not a superuser at the end; the last row decides the business and data domain role and the Superset roles
batch-import/last-record-wins.spec.ts:56 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 6.9 s
passed
ends an existing user with the last row, whatever it had before
an existing user is imported again with two rows; the result is the last row, the viewer role with the RLS_B role, whatever the user had before and without dashboards
batch-import/last-record-wins.spec.ts:70 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 9.7 s
Batch import - new users
HELLODATA-2073 (roles in the subsystems) and HELLODATA-2074 (roles in HelloDATA): users of the csv file that do not exist yet are added to the portal and to Superset, with the roles of the file
passed
adds a viewer with its dashboard and RLS roles
admin imports a file (with a byte order mark, as saved by Excel) for a new viewer; the user exists, has the roles of the file and its dashboard in the portal and in Superset, and is listed in the user management
batch-import/new-users.spec.ts:44 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 8.2 s
passed
maps the data domain role of each user to the BI roles of Superset
a file with a business specialist, an editor and a data domain admin; each gets the matching BI roles in Superset and the default comment permission, and only the data domain admin may comment
batch-import/new-users.spec.ts:66 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 7.6 s
passed
makes business domain admins data domain admins everywhere
a business domain admin and a HelloDATA admin in the file become data domain admins everywhere; the HelloDATA admin is a superuser and also Admin in Superset
batch-import/new-users.spec.ts:89 all actions in the report
 HELLODATA-2073
HELLODATA-2074		 7.3 s

comments

StatusTestJiraDuration
Delete comments
deleting dashboard comments as author and as reviewer
passed
an author deletes its own draft
an editor writes a comment and deletes it with a reason: it leaves the feed, but the author still finds it among the deleted comments, where it cannot be deleted again
comments/comment-deletion.spec.ts:37 all actions in the report
 HELLODATA-2932 17.3 s
passed
a reviewer deletes the active version and the last published one is shown again
a reviewer edits a published comment and deletes the new version: the first published version is shown again, and other users (editor, viewer) cannot delete the comment
  1. only the author and reviewers may delete a comment
comments/comment-deletion.spec.ts:61 all actions in the report
 HELLODATA-2932 41.3 s
passed
a reviewer deletes a comment with all its versions
a reviewer deletes a comment with all its versions: nothing is left in the feed, and the deleted comment shows the reason and both versions in its history
comments/comment-deletion.spec.ts:94 all actions in the report
 HELLODATA-2931 22.4 s
Comments filtering
the admin filters the comments of a dashboard
passed
filters the comments by status, quarter, tag and year
the admin creates a draft with a tag in Q1 and a published comment in Q2, then filters by status, quarter, tag and year and sees only the matching comment each time
  1. status
  2. quarter
  3. tag
  4. year
comments/comment-filtering.spec.ts:20 all actions in the report
 HELLODATA-2945 44.6 s
Commenting permissions
which roles can see and write comments, by default and after an admin changed the permission
passed
HELLODATA_ADMIN can read and write comments
a HELLODATA, business domain or data domain admin opens the comments of a dashboard and sees the new comment input and the export and import buttons
comments/comment-permissions.spec.ts:47 all actions in the report
 HELLODATA-4070 8.5 s
passed
BUSINESS_DOMAIN_ADMIN can read and write comments
a HELLODATA, business domain or data domain admin opens the comments of a dashboard and sees the new comment input and the export and import buttons
comments/comment-permissions.spec.ts:47 all actions in the report
 HELLODATA-4070 8.8 s
passed
DATA_DOMAIN_ADMIN can read and write comments
a HELLODATA, business domain or data domain admin opens the comments of a dashboard and sees the new comment input and the export and import buttons
comments/comment-permissions.spec.ts:47 all actions in the report
 HELLODATA-4070 6.7 s
Commenting permissions › DATA_DOMAIN_EDITOR
which roles can see and write comments, by default and after an admin changed the permission a role without comment permission by default
passed
sees no comments without a comment permission
the user opens a dashboard and sees no comments panel as long as no comment permission was granted
comments/comment-permissions.spec.ts:70 all actions in the report
 HELLODATA-4070 7.1 s
Commenting permissions › DATA_DOMAIN_VIEWER
which roles can see and write comments, by default and after an admin changed the permission a role without comment permission by default
passed
sees no comments without a comment permission
the user opens a dashboard and sees no comments panel as long as no comment permission was granted
comments/comment-permissions.spec.ts:70 all actions in the report
 HELLODATA-4070 6.1 s
Commenting permissions › DATA_DOMAIN_BUSINESS_SPECIALIST
which roles can see and write comments, by default and after an admin changed the permission a role without comment permission by default
passed
sees no comments without a comment permission
the user opens a dashboard and sees no comments panel as long as no comment permission was granted
comments/comment-permissions.spec.ts:70 all actions in the report
 HELLODATA-4070 5.4 s
Edit commenting permissions
the admin edits the comment permission of users
passed
review includes write and read
in the user edit page of the editor, ticking review also ticks write and read, which can then not be unticked (nothing is saved)
comments/comment-permissions.spec.ts:85 all actions in the report
 HELLODATA-4071 3.9 s
passed
the comment permissions of a business domain admin cannot be changed
in the user edit page of a business domain admin read, write and review are ticked and cannot be changed
comments/comment-permissions.spec.ts:100 all actions in the report
 HELLODATA-4071 5.1 s
Edit commenting permissions › DATA_DOMAIN_EDITOR
the admin edits the comment permission of users a role whose comment access an admin changes step by step
passed
gets the comment access an admin grants
an admin grants read, write, review and finally none to the user, who then sees: comments without writing, writing without export and import, the same with review, and no comments panel at the end
  1. read: sees the comments, cannot write
  2. write: can write comments, cannot export or import them
  3. review: cannot export or import without the DASHBOARD_COMMENTS_IMPORT_EXPORT portal permission
  4. none: the comments panel is gone again
comments/comment-permissions.spec.ts:127 all actions in the report
 HELLODATA-4071 46.4 s
Edit commenting permissions › DATA_DOMAIN_VIEWER
the admin edits the comment permission of users a role whose comment access an admin changes step by step
passed
gets the comment access an admin grants
an admin grants read, write, review and finally none to the user, who then sees: comments without writing, writing without export and import, the same with review, and no comments panel at the end
  1. read: sees the comments, cannot write
  2. write: can write comments, cannot export or import them
  3. review: cannot export or import without the DASHBOARD_COMMENTS_IMPORT_EXPORT portal permission
  4. none: the comments panel is gone again
comments/comment-permissions.spec.ts:127 all actions in the report
 HELLODATA-4071 47.6 s
Edit commenting permissions › DATA_DOMAIN_BUSINESS_SPECIALIST
the admin edits the comment permission of users a role whose comment access an admin changes step by step
passed
gets the comment access an admin grants
an admin grants read, write, review and finally none to the user, who then sees: comments without writing, writing without export and import, the same with review, and no comments panel at the end
  1. read: sees the comments, cannot write
  2. write: can write comments, cannot export or import them
  3. review: cannot export or import without the DASHBOARD_COMMENTS_IMPORT_EXPORT portal permission
  4. none: the comments panel is gone again
comments/comment-permissions.spec.ts:127 all actions in the report
 HELLODATA-4071 45.2 s
Comment review
the review of comments between an editor (author), a data domain admin (reviewer) and a viewer (reader)
passed
an author sends a draft for review
an editor writes a draft: only the author sees it and cannot publish it, after sending it for review it is locked for the author, the reviewer can publish or decline it and the reader still does not see it
  1. a draft is only visible to its author
  2. the reviewer sees the comment and can publish or decline it
  3. the reader still does not see it
comments/comment-review.spec.ts:48 all actions in the report
 HELLODATA-2933 40.9 s
passed
a reviewer publishes a comment
a reviewer publishes a comment sent for review, then the reader sees it, but cannot edit, publish or delete it
  1. the reader sees the published comment
comments/comment-review.spec.ts:92 all actions in the report
 HELLODATA-2946 41.7 s
passed
a reviewer declines a comment with a reason
a reviewer declines a comment with a reason: the author sees the reason and can edit it again, the reader does not see the comment
  1. the author sees the decline reason and can edit the comment again
  2. the reader does not see the declined comment
comments/comment-review.spec.ts:119 all actions in the report
 HELLODATA-2946 50.2 s
Restore a comment version
restoring an earlier version of a comment
passed
a reviewer restores an earlier published version
a reviewer publishes a second version of a comment and restores the first one: it is active again and the second stays in the history, a writer who is not the author sees neither details nor versions
  1. a writer who is not the author sees neither details nor versions
comments/comment-versions.spec.ts:34 all actions in the report
 HELLODATA-2947 33.5 s
All Dashboards Comments menu
HELLODATA-4072: the domain-wide comments overview is a review tool
passed
is available to HELLODATA_ADMIN
the user opens the domain comments page (menu entry All Dashboards Comments) and sees its heading and Dashboard column
comments/domain-comments.spec.ts:36 all actions in the report
 HELLODATA-4072 4.5 s
passed
is available to BUSINESS_DOMAIN_ADMIN
the user opens the domain comments page (menu entry All Dashboards Comments) and sees its heading and Dashboard column
comments/domain-comments.spec.ts:36 all actions in the report
 HELLODATA-4072 4.4 s
passed
is available to DATA_DOMAIN_ADMIN
the user opens the domain comments page (menu entry All Dashboards Comments) and sees its heading and Dashboard column
comments/domain-comments.spec.ts:36 all actions in the report
 HELLODATA-4072 3.6 s
All Dashboards Comments menu › DATA_DOMAIN_EDITOR
HELLODATA-4072: the domain-wide comments overview is a review tool a role that gets the domain comments page only with the review permission
passed
gets the menu only with the review permission
with write permission the user has no domain comments menu entry, with review permission the entry and page are there
  1. write: no menu
  2. review: menu and overview page
comments/domain-comments.spec.ts:57 all actions in the report
 HELLODATA-4072 17.0 s
All Dashboards Comments menu › DATA_DOMAIN_VIEWER
HELLODATA-4072: the domain-wide comments overview is a review tool a role that gets the domain comments page only with the review permission
passed
gets the menu only with the review permission
with write permission the user has no domain comments menu entry, with review permission the entry and page are there
  1. write: no menu
  2. review: menu and overview page
comments/domain-comments.spec.ts:57 all actions in the report
 HELLODATA-4072 21.0 s
All Dashboards Comments menu › DATA_DOMAIN_BUSINESS_SPECIALIST
HELLODATA-4072: the domain-wide comments overview is a review tool a role that gets the domain comments page only with the review permission
passed
gets the menu only with the review permission
with write permission the user has no domain comments menu entry, with review permission the entry and page are there
  1. write: no menu
  2. review: menu and overview page
comments/domain-comments.spec.ts:57 all actions in the report
 HELLODATA-4072 21.0 s

dashboards

StatusTestJiraDuration
Available dashboards - DATA_DOMAIN_VIEWER
a viewer or business specialist only sees the dashboards an admin gave them access to
passed
sees no dashboard without access
without dashboard access the user sees no dashboard in the Dashboards menu and no link to the Superset instance
dashboards/available-dashboards.spec.ts:23 all actions in the report
 6.8 s
passed
sees and opens a dashboard after the admin gave access
after an admin gave access the user sees the dashboard in the list and menu and can open it with its content visible
dashboards/available-dashboards.spec.ts:34 all actions in the report
 10.1 s
Available dashboards - DATA_DOMAIN_BUSINESS_SPECIALIST
a viewer or business specialist only sees the dashboards an admin gave them access to
passed
sees no dashboard without access
without dashboard access the user sees no dashboard in the Dashboards menu and no link to the Superset instance
dashboards/available-dashboards.spec.ts:23 all actions in the report
 8.1 s
passed
sees and opens a dashboard after the admin gave access
after an admin gave access the user sees the dashboard in the list and menu and can open it with its content visible
dashboards/available-dashboards.spec.ts:34 all actions in the report
 10.8 s
Dashboard access log
HELLODATA admins see who opened which dashboard of a data domain, and when, in Administration -> Dashboard access
passed
lists a user who opened a dashboard
an editor opens a dashboard, then the admin finds a row with that user and dashboard in the dashboard access list (the list is filled by a sync, so the test retries for a few minutes)
dashboards/dashboard-access-log.spec.ts:20 all actions in the report
 9.0 s
Dashboard filters - DATA_DOMAIN_ADMIN
admins and editors may change the embedded dashboard and its filters
passed
can edit the dashboard
a dashboard admin or editor opens a dashboard and edits it: the Save button appears, then Discard leaves the edit mode
dashboards/dashboard-filters.spec.ts:33 all actions in the report
 6.6 s
passed
can add and edit filters
a dashboard admin or editor opens the filter settings (gear) of a dashboard and sees the dialog to add and edit filters
dashboards/dashboard-filters.spec.ts:44 all actions in the report
 9.9 s
Dashboard filters - DATA_DOMAIN_EDITOR
admins and editors may change the embedded dashboard and its filters
passed
can edit the dashboard
a dashboard admin or editor opens a dashboard and edits it: the Save button appears, then Discard leaves the edit mode
dashboards/dashboard-filters.spec.ts:33 all actions in the report
 6.4 s
passed
can add and edit filters
a dashboard admin or editor opens the filter settings (gear) of a dashboard and sees the dialog to add and edit filters
dashboards/dashboard-filters.spec.ts:44 all actions in the report
 9.1 s
Dashboard filters - DATA_DOMAIN_VIEWER
viewers and business specialists with dashboard access may use the filters but not change them
passed
cannot edit the dashboard or its filters
a viewer or business specialist opens a dashboard: the filters can be applied, but there is no Edit dashboard button and no filter settings gear
dashboards/dashboard-filters.spec.ts:80 all actions in the report
 5.6 s
Dashboard filters - DATA_DOMAIN_BUSINESS_SPECIALIST
viewers and business specialists with dashboard access may use the filters but not change them
passed
cannot edit the dashboard or its filters
a viewer or business specialist opens a dashboard: the filters can be applied, but there is no Edit dashboard button and no filter settings gear
dashboards/dashboard-filters.spec.ts:80 all actions in the report
 6.2 s
Dashboard groups
An admin groups dashboards and users of a data domain in its dashboard group page: every member of a group gets the dashboards of the group, and loses them again when the group is deleted
passed
admin creates a group with a dashboard and a viewer
the admin creates a dashboard group with the showcase dashboard and the viewer as member, then sees it in the list with the dashboard and one user
dashboards/dashboard-groups.spec.ts:36 all actions in the report
 6.9 s
passed
the viewer sees the dashboard of its group
the viewer, who has no direct access, sees the showcase dashboard through the dashboard group
dashboards/dashboard-groups.spec.ts:61 all actions in the report
 2.8 s
passed
admin deletes the group and the viewer loses the dashboard
the admin deletes the dashboard group, it disappears from the list and the viewer no longer sees the dashboard
dashboards/dashboard-groups.spec.ts:66 all actions in the report
 8.0 s
Dashboard metadata - DATA_DOMAIN_ADMIN
admins and editors may edit the metadata of a dashboard
passed
can edit the metadata of a dashboard
a dashboard admin or editor changes the business process of a dashboard in the dashboard list and sees it saved, also after reloading the list, then the value is cleared again
dashboards/dashboard-metadata.spec.ts:39 all actions in the report
 10.1 s
Dashboard metadata - DATA_DOMAIN_EDITOR
admins and editors may edit the metadata of a dashboard
passed
can edit the metadata of a dashboard
a dashboard admin or editor changes the business process of a dashboard in the dashboard list and sees it saved, also after reloading the list, then the value is cleared again
dashboards/dashboard-metadata.spec.ts:39 all actions in the report
 9.8 s
Dashboard metadata - DATA_DOMAIN_VIEWER
viewers and business specialists with dashboard access may only look at the metadata of a dashboard
passed
cannot edit the metadata of a dashboard
a viewer or business specialist sees the open button in the dashboard list, but the edit button of the metadata is hidden
dashboards/dashboard-metadata.spec.ts:73 all actions in the report
 2.7 s
Dashboard metadata - DATA_DOMAIN_BUSINESS_SPECIALIST
viewers and business specialists with dashboard access may only look at the metadata of a dashboard
passed
cannot edit the metadata of a dashboard
a viewer or business specialist sees the open button in the dashboard list, but the edit button of the metadata is hidden
dashboards/dashboard-metadata.spec.ts:73 all actions in the report
 3.3 s
Draft dashboards
HELLODATA-701: a dashboard turned into a draft in Superset disappears from the Dashboards menu and list
passed
are not available to a viewer
a viewer sees the dashboard, then an editor turns it into a draft in Superset: after the sync the dashboard is gone from the viewer's list and Dashboards menu (it is published again at the end)
dashboards/draft-dashboards.spec.ts:27 all actions in the report
 HELLODATA-701 113.3 s

data-eng

StatusTestJiraDuration
DWH Viewer › HELLODATA_ADMIN
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the CloudBeaver access of this role
passed
opens CloudBeaver logged in from the DWH Viewer
the user opens the DWH Viewer; CloudBeaver is shown in its iframe and the user is already logged in, without a login prompt of CloudBeaver
data-eng/dwh-viewer.spec.ts:52 all actions in the report
 HELLODATA-855 13.6 s
passed
sees only the connections of its role in the DataMarts Viewer
the user opens the DataMarts Viewer and sees exactly the CloudBeaver connections of its role, no other ones
data-eng/dwh-viewer.spec.ts:72 all actions in the report
 7.3 s
DWH Viewer › BUSINESS_DOMAIN_ADMIN
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the CloudBeaver access of this role
passed
opens CloudBeaver logged in from the DWH Viewer
the user opens the DWH Viewer; CloudBeaver is shown in its iframe and the user is already logged in, without a login prompt of CloudBeaver
data-eng/dwh-viewer.spec.ts:52 all actions in the report
 HELLODATA-855 9.2 s
passed
sees only the connections of its role in the DataMarts Viewer
the user opens the DataMarts Viewer and sees exactly the CloudBeaver connections of its role, no other ones
data-eng/dwh-viewer.spec.ts:72 all actions in the report
 6.6 s
passed
cannot create connections in CloudBeaver
the user opens the DataMarts Viewer and cannot create a connection, the New Connection button is not there
data-eng/dwh-viewer.spec.ts:85 all actions in the report
 7.4 s
DWH Viewer › DATA_DOMAIN_ADMIN
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the CloudBeaver access of this role
passed
opens CloudBeaver logged in from the DWH Viewer
the user opens the DWH Viewer; CloudBeaver is shown in its iframe and the user is already logged in, without a login prompt of CloudBeaver
data-eng/dwh-viewer.spec.ts:52 all actions in the report
 HELLODATA-855 8.5 s
passed
sees only the connections of its role in the DataMarts Viewer
the user opens the DataMarts Viewer and sees exactly the CloudBeaver connections of its role, no other ones
data-eng/dwh-viewer.spec.ts:72 all actions in the report
 6.9 s
passed
cannot create connections in CloudBeaver
the user opens the DataMarts Viewer and cannot create a connection, the New Connection button is not there
data-eng/dwh-viewer.spec.ts:85 all actions in the report
 6.4 s
DWH Viewer › DATA_DOMAIN_EDITOR
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the CloudBeaver access of this role
passed
has no DWH Viewer
the user has no DWH Viewer entry in the menu and the page of the DWH Viewer redirects to the forbidden page
data-eng/dwh-viewer.spec.ts:64 all actions in the report
 3.5 s
passed
sees only the connections of its role in the DataMarts Viewer
the user opens the DataMarts Viewer and sees exactly the CloudBeaver connections of its role, no other ones
data-eng/dwh-viewer.spec.ts:72 all actions in the report
 5.8 s
passed
cannot create connections in CloudBeaver
the user opens the DataMarts Viewer and cannot create a connection, the New Connection button is not there
data-eng/dwh-viewer.spec.ts:85 all actions in the report
 7.8 s
DWH Viewer › DATA_DOMAIN_BUSINESS_SPECIALIST
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the CloudBeaver access of this role
passed
has no DWH Viewer
the user has no DWH Viewer entry in the menu and the page of the DWH Viewer redirects to the forbidden page
data-eng/dwh-viewer.spec.ts:64 all actions in the report
 2.9 s
passed
sees only the connections of its role in the DataMarts Viewer
the user opens the DataMarts Viewer and sees exactly the CloudBeaver connections of its role, no other ones
data-eng/dwh-viewer.spec.ts:72 all actions in the report
 6.0 s
passed
cannot create connections in CloudBeaver
the user opens the DataMarts Viewer and cannot create a connection, the New Connection button is not there
data-eng/dwh-viewer.spec.ts:85 all actions in the report
 6.1 s
DWH Viewer › DATA_DOMAIN_VIEWER
the DWH Viewer and the DataMarts Viewer (CloudBeaver) of each role: who gets them, which connections are visible the viewer has neither DATA_DWH nor DATA_MARTS (page-access.spec.ts checks the urls of both)
passed
has no DWH Viewer
the data domain viewer has no DWH Viewer entry in the menu and its page redirects to the forbidden page
data-eng/dwh-viewer.spec.ts:97 all actions in the report
 2.7 s
Filebrowser
HELLODATA-2004: the Filebrowser is SFTPGo, which shows each data domain the user has a role in as a folder. Data domain admins may do everything there, editors may create and rename but not delete, viewers may only read.
passed
admin creates, renames and deletes a folder
the user opens the Filebrowser, creates a folder in the data domain folder, renames it, sees it after reopening the folder and deletes it
data-eng/filebrowser.spec.ts:33 all actions in the report
 HELLODATA-2004 9.4 s
passed
default-data-domain-admin@hellodata.ch creates, renames and deletes a folder
the user opens the Filebrowser, creates a folder in the data domain folder, renames it, sees it after reopening the folder and deletes it
data-eng/filebrowser.spec.ts:33 all actions in the report
 HELLODATA-2004 9.9 s
passed
default-data-domain-editor@hellodata.ch creates and renames a folder, but cannot delete it
the data domain editor creates and renames a folder in the Filebrowser but has no delete action; the data domain admin removes the left over folders afterwards
data-eng/filebrowser.spec.ts:51 all actions in the report
 HELLODATA-2004 13.5 s
passed
default-data-domain-business_specialist@hellodata.ch has no Filebrowser
the user has no Filebrowser entry in the menu
data-eng/filebrowser.spec.ts:78 all actions in the report
 HELLODATA-2004 2.3 s
passed
default-data-domain-viewer@hellodata.ch has no Filebrowser
the user has no Filebrowser entry in the menu
data-eng/filebrowser.spec.ts:78 all actions in the report
 HELLODATA-2004 2.7 s
Orchestration
the Orchestration page and who may open it: Orchestration for Airflow 2, Orchestration (Airflow3) for Airflow 3 (the Airflow of the Playwright project, the @airflow tag runs it for each)
passed
admin opens Airflow with the DAGs of the data domain
the admin opens Orchestration; Airflow is shown with the DAG of the data domain in the list
data-eng/orchestration.spec.ts:18 all actions in the report
 HELLODATA-755 3.9 s
passed
hellodata-product-development-admin@hellodata.ch opens Airflow with the DAGs of the data domain
the user opens Orchestration and Airflow is shown
data-eng/orchestration.spec.ts:28 all actions in the report
 HELLODATA-755 3.9 s
passed
default-data-domain-admin@hellodata.ch opens Airflow with the DAGs of the data domain
the user opens Orchestration and Airflow is shown
data-eng/orchestration.spec.ts:28 all actions in the report
 HELLODATA-755 4.3 s
passed
default-data-domain-editor@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 3.3 s
passed
default-data-domain-business_specialist@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 2.9 s
passed
default-data-domain-viewer@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 3.2 s
passed
breadcrumb shows Orchestration on the DAG list
the admin opens Orchestration and the breadcrumb shows Orchestration
data-eng/orchestration.spec.ts:49 all actions in the report
 HELLODATA-848 3.6 s
passed
breadcrumb leads from a DAG back to the DAG list
the admin opens the details of a DAG; the breadcrumb Orchestration leads back to the DAG list of Airflow
data-eng/orchestration.spec.ts:56 all actions in the report
 HELLODATA-848 4.4 s
Airflow 3 › Orchestration
the Orchestration page and who may open it: Orchestration for Airflow 2, Orchestration (Airflow3) for Airflow 3 (the Airflow of the Playwright project, the @airflow tag runs it for each)
passed
admin opens Airflow with the DAGs of the data domain
the admin opens Orchestration; Airflow is shown with the DAG of the data domain in the list
data-eng/orchestration.spec.ts:18 all actions in the report
 HELLODATA-755 4.8 s
passed
hellodata-product-development-admin@hellodata.ch opens Airflow with the DAGs of the data domain
the user opens Orchestration and Airflow is shown
data-eng/orchestration.spec.ts:28 all actions in the report
 HELLODATA-755 5.5 s
passed
default-data-domain-admin@hellodata.ch opens Airflow with the DAGs of the data domain
the user opens Orchestration and Airflow is shown
data-eng/orchestration.spec.ts:28 all actions in the report
 HELLODATA-755 4.4 s
passed
default-data-domain-editor@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 3.0 s
passed
default-data-domain-business_specialist@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 3.5 s
passed
default-data-domain-viewer@hellodata.ch has no orchestration
the user has no Orchestration entry in the menu and its page redirects to the forbidden page
data-eng/orchestration.spec.ts:38 all actions in the report
 HELLODATA-755 2.9 s
passed
breadcrumb shows Orchestration on the DAG list
the admin opens Orchestration and the breadcrumb shows Orchestration
data-eng/orchestration.spec.ts:49 all actions in the report
 HELLODATA-848 4.2 s
passed
breadcrumb leads from a DAG back to the DAG list
the admin opens the details of a DAG; the breadcrumb Orchestration leads back to the DAG list of Airflow
data-eng/orchestration.spec.ts:56 all actions in the report
 HELLODATA-848 6.2 s
Pipeline status
HELLODATA-745: a user sees the DAG status (Status -> Data pipelines on the summary page) only of the data domains the user has a role in. The portal assigns a DAG to a data domain by the data domain key in the path of the DAG file. HELLODATA-2184: only DAGs with a visible tag (PROD) are listed, so neither an untagged DAG nor the showcase DAG are. The DAGs are written into the Airflow of the Playwright project (the @airflow tag runs it for each Airflow).
passed
admin sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 12.9 s
passed
hellodata-product-development-admin@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.6 s
passed
default-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 3.2 s
passed
default-data-domain-editor@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.5 s
passed
default-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.7 s
passed
status panel lists the DAGs of the data domain
the admin opens the summary page and the status panel Data pipelines lists the DAG of the data domain but not the DAG of the foreign data domain; the badge next to the DAG names the Airflow it runs in (AF2 or AF3)
data-eng/pipeline-status.spec.ts:60 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.6 s
Airflow 3 › Pipeline status
HELLODATA-745: a user sees the DAG status (Status -> Data pipelines on the summary page) only of the data domains the user has a role in. The portal assigns a DAG to a data domain by the data domain key in the path of the DAG file. HELLODATA-2184: only DAGs with a visible tag (PROD) are listed, so neither an untagged DAG nor the showcase DAG are. The DAGs are written into the Airflow of the Playwright project (the @airflow tag runs it for each Airflow).
passed
admin sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.5 s
passed
hellodata-product-development-admin@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 13.1 s
passed
default-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.9 s
passed
default-data-domain-editor@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.9 s
passed
default-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the user sees the tagged DAG of its own data domain in the pipeline status, but not the DAG of a data domain it has no role in, nor the untagged DAG and the (untagged) showcase DAG of its own data domain
data-eng/pipeline-status.spec.ts:51 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.6 s
passed
status panel lists the DAGs of the data domain
the admin opens the summary page and the status panel Data pipelines lists the DAG of the data domain but not the DAG of the foreign data domain; the badge next to the DAG names the Airflow it runs in (AF2 or AF3)
data-eng/pipeline-status.spec.ts:60 all actions in the report
 HELLODATA-745
HELLODATA-2184		 2.7 s

portal

StatusTestJiraDuration
Authentication
login with Keycloak, a wrong password and logout of the portal
passed
admin logs in through Keycloak and lands on the home page
the admin opens the portal, logs in on the Keycloak form and lands on the home page, where the top bar shows the admin's email
portal/auth.spec.ts:7 all actions in the report
 1.9 s
passed
wrong password is rejected by Keycloak
the admin logs in with a wrong password; Keycloak shows an error and keeps the login form
portal/auth.spec.ts:13 all actions in the report
 1.8 s
passed
logout ends the session
the admin logs out from the user menu and sees the login form; opening a portal url afterwards leads to the login form again, so the session is gone
portal/auth.spec.ts:22 all actions in the report
 5.9 s
Data domain isolation
A user with a role in one data domain sees nothing of another one: neither in the data domain selector, nor its dashboards, its DAGs or its CloudBeaver connections. The e2e installation has the Default Data Domain with Superset and the Extra Data Domain without (compose-override.yaml), and both share Airflow and CloudBeaver.
passed
extra-data-domain-admin@hellodata.ch sees no dashboards of the Default Data Domain
only the Default Data Domain has Superset, so its dashboards must not leak into the other one
portal/data-domain-isolation.spec.ts:82 all actions in the report
 2.8 s
Data domain isolation › Default Data Domain
A user with a role in one data domain sees nothing of another one: neither in the data domain selector, nor its dashboards, its DAGs or its CloudBeaver connections. The e2e installation has the Default Data Domain with Superset and the Extra Data Domain without (compose-override.yaml), and both share Airflow and CloudBeaver. checks that the admin of this data domain sees only its own data and nothing of the other one
passed
default-data-domain-admin@hellodata.ch cannot choose the Extra Data Domain
the data domain admin has a role in this data domain only: the selector shows it and offers nothing to choose, so neither the other data domain
portal/data-domain-isolation.spec.ts:58 all actions in the report
 HELLODATA-662 3.2 s
passed
default-data-domain-admin@hellodata.ch sees only the CloudBeaver connections of its data domain
the data domain admin opens the Data Marts viewer (CloudBeaver); the connections of its data domain are listed, the ones of the other data domain are not
portal/data-domain-isolation.spec.ts:66 all actions in the report
 6.9 s
Data domain isolation › Extra Data Domain
A user with a role in one data domain sees nothing of another one: neither in the data domain selector, nor its dashboards, its DAGs or its CloudBeaver connections. The e2e installation has the Default Data Domain with Superset and the Extra Data Domain without (compose-override.yaml), and both share Airflow and CloudBeaver. checks that the admin of this data domain sees only its own data and nothing of the other one
passed
extra-data-domain-admin@hellodata.ch cannot choose the Default Data Domain
the data domain admin has a role in this data domain only: the selector shows it and offers nothing to choose, so neither the other data domain
portal/data-domain-isolation.spec.ts:58 all actions in the report
 HELLODATA-662 7.8 s
passed
extra-data-domain-admin@hellodata.ch sees only the CloudBeaver connections of its data domain
the data domain admin opens the Data Marts viewer (CloudBeaver); the connections of its data domain are listed, the ones of the other data domain are not
portal/data-domain-isolation.spec.ts:66 all actions in the report
 7.0 s
Data domain isolation of the DAGs › Default Data Domain
The DAGs of a data domain are listed only to its users, in the Airflow of the Playwright project (the @airflow tag runs it for each Airflow): each data domain gets a DAG of its own (tagged PROD, the only DAGs the portal lists). checks that the admin and the viewer of this data domain see only its own DAGs and none of the other one
passed
default-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the data domain admin opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:135 all actions in the report
 2.8 s
passed
default-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the data domain viewer opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:144 all actions in the report
 2.5 s
Airflow 3 › Data domain isolation of the DAGs › Default Data Domain
The DAGs of a data domain are listed only to its users, in the Airflow of the Playwright project (the @airflow tag runs it for each Airflow): each data domain gets a DAG of its own (tagged PROD, the only DAGs the portal lists). checks that the admin and the viewer of this data domain see only its own DAGs and none of the other one
passed
default-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the data domain admin opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:135 all actions in the report
 2.4 s
passed
default-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the data domain viewer opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:144 all actions in the report
 2.5 s
Data domain isolation of the DAGs › Extra Data Domain
The DAGs of a data domain are listed only to its users, in the Airflow of the Playwright project (the @airflow tag runs it for each Airflow): each data domain gets a DAG of its own (tagged PROD, the only DAGs the portal lists). checks that the admin and the viewer of this data domain see only its own DAGs and none of the other one
passed
extra-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the data domain admin opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:135 all actions in the report
 2.7 s
passed
extra-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the data domain viewer opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:144 all actions in the report
 4.0 s
Airflow 3 › Data domain isolation of the DAGs › Extra Data Domain
The DAGs of a data domain are listed only to its users, in the Airflow of the Playwright project (the @airflow tag runs it for each Airflow): each data domain gets a DAG of its own (tagged PROD, the only DAGs the portal lists). checks that the admin and the viewer of this data domain see only its own DAGs and none of the other one
passed
extra-data-domain-admin@hellodata.ch sees only the DAGs of its data domain
the data domain admin opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:135 all actions in the report
 2.6 s
passed
extra-data-domain-viewer@hellodata.ch sees only the DAGs of its data domain
the data domain viewer opens the pipelines status; the DAGs of its data domain are listed, not of the other data domain
portal/data-domain-isolation.spec.ts:144 all actions in the report
 4.0 s
Data domain selector
the data domain selector in the top bar: choosable data domains, filtering of dashboards, keeping the selection
passed
admin chooses between all data domains
the admin starts with all data domains; the selector menu lists the other data domains and never the selected one, and after choosing the Default Data Domain the menu offers all data domains again
portal/data-domain-selector.spec.ts:34 all actions in the report
 2.6 s
passed
default-data-domain-admin@hellodata.ch has only its own data domain
the data domain admin has a role in one data domain only: the top bar shows that data domain, without All Data Domains and without a menu to choose another one
portal/data-domain-selector.spec.ts:53 all actions in the report
 HELLODATA-662 2.1 s
passed
the selected data domain filters the dashboards
the admin selects the Extra Data Domain, which has no dashboards: the list says no dashboards found and the Dashboards menu is empty; selecting the Default Data Domain shows the dashboards again
portal/data-domain-selector.spec.ts:60 all actions in the report
 5.6 s
passed
the selected data domain is kept after a reload
the admin selects a data domain and then all data domains; after each page reload the selector still shows that choice
portal/data-domain-selector.spec.ts:84 all actions in the report
 4.4 s
Navigation
the admin opens the administration pages from the menu and the home page shows its panels without errors which menu entries each role sees is covered by administration/roles.spec.ts
passed
administration menu opens User management
the admin opens this entry of the Administration menu; the page url changes and its heading is shown
portal/navigation.spec.ts:16 all actions in the report
 3.0 s
passed
administration menu opens Portal role management
the admin opens this entry of the Administration menu; the page url changes and its heading is shown
portal/navigation.spec.ts:16 all actions in the report
 3.2 s
passed
administration menu opens Notifications
the admin opens this entry of the Administration menu; the page url changes and its heading is shown
portal/navigation.spec.ts:16 all actions in the report
 4.4 s
passed
administration menu opens FAQ management
the admin opens this entry of the Administration menu; the page url changes and its heading is shown
portal/navigation.spec.ts:16 all actions in the report
 2.6 s
passed
administration menu opens Documentation management
the admin opens this entry of the Administration menu; the page url changes and its heading is shown
portal/navigation.spec.ts:16 all actions in the report
 3.2 s
passed
home page shows the overview panels
the admin sees the overview panels on the home page: dashboards, external dashboards, data marts, lineage, FAQ and documentation
portal/navigation.spec.ts:25 all actions in the report
 2.4 s
passed
home page loads the lineage docs without errors
the admin opens the home page; the request for the lineage docs succeeds and no error message is shown
portal/navigation.spec.ts:33 all actions in the report
 2.6 s

superset

StatusTestJiraDuration
Dashboard export and import
exporting a dashboard as zip from the import-export page and importing it again HELLODATA-1318 and HELLODATA-1319
passed
exports a dashboard as zip
the admin selects the dashboard on the import-export page and exports it; Superset returns a zip file
superset/dashboard-export-import.spec.ts:40 all actions in the report
 HELLODATA-1318
HELLODATA-1319		 7.3 s
passed
imports an exported dashboard
the admin exports the dashboard and uploads the zip again for the data domain without removing orphaned charts; the upload succeeds and the dashboard is still listed
superset/dashboard-export-import.spec.ts:48 all actions in the report
 HELLODATA-1318
HELLODATA-1319		 11.2 s
passed
DATA_DOMAIN_ADMIN opens the Superset instance of its data domain
the user opens the Superset instance of its data domain from the Dashboards menu; Superset is shown with its Dashboards menu and lists the showcase dashboard
superset/superset-access.spec.ts:22 all actions in the report
 6.0 s
passed
DATA_DOMAIN_EDITOR opens the Superset instance of its data domain
the user opens the Superset instance of its data domain from the Dashboards menu; Superset is shown with its Dashboards menu and lists the showcase dashboard
superset/superset-access.spec.ts:22 all actions in the report
 4.9 s
DATA_DOMAIN_VIEWER
a viewer role that has access to a dashboard but no access to the Superset instance itself
passed
has no link to the Superset instance
the user has access to the showcase dashboard, which is in the Dashboards menu, but the menu has no Open Superset Instance entry
superset/superset-access.spec.ts:48 all actions in the report
 3.3 s
DATA_DOMAIN_BUSINESS_SPECIALIST
a viewer role that has access to a dashboard but no access to the Superset instance itself
passed
has no link to the Superset instance
the user has access to the showcase dashboard, which is in the Dashboards menu, but the menu has no Open Superset Instance entry
superset/superset-access.spec.ts:48 all actions in the report
 3.0 s
Superset language › DATA_DOMAIN_EDITOR (BI_EDITOR)
the embedded Superset dashboard is shown in the language chosen in the portal, for the BI roles the dashboard language checked with a user of this role
passed
sees the dashboard in the language of the portal
the user opens the dashboard and switches the portal to German; after reloading, Superset shows its German texts (Filter anwenden, not Apply filters) and all language pack requests succeed
superset/superset-language.spec.ts:31 all actions in the report
 9.3 s
Superset language › DATA_DOMAIN_VIEWER (BI_VIEWER)
the embedded Superset dashboard is shown in the language chosen in the portal, for the BI roles the dashboard language checked with a user of this role
passed
sees the dashboard in the language of the portal
the user opens the dashboard and switches the portal to German; after reloading, Superset shows its German texts (Filter anwenden, not Apply filters) and all language pack requests succeed
superset/superset-language.spec.ts:31 all actions in the report
 8.4 s

Tested images

ImageDigest
bedag/hello-data-airflow:airflow3-1.7.0-dev-SNAPSHOTsha256:88ceb07a7651d5acb5fc48a97eff39b2adf95db0e917381c6cd25b17ea074539
bedag/hello-data-cloudbeaver-gateway:1.7.0-dev-SNAPSHOTsha256:431605cd5064b1d9e5c6e89ab9bc48bf9f70ca36d2b12fd8f00900231b3b27d7
bedag/hello-data-dbt-docs:1.7.0-dev-SNAPSHOTsha256:8cfdce01e5dcc4308c75d67cf74aa7e88889d79932d2af666e063be516cc68f9
bedag/hello-data-dc-airflow:1.7.0-dev-SNAPSHOTsha256:bf6a24adbfef3b18d7fc40bada128973014e241da1b61bc84882ff4652fa4950
bedag/hello-data-dc-cloudbeaver:1.7.0-dev-SNAPSHOTsha256:f119289435fe0ca8faa13689d20ecc3d7406f564381874138f878c355382db71
bedag/hello-data-dc-keycloak:1.7.0-dev-SNAPSHOTsha256:40556ab7548af60d65d8ce993bed4726b7ef37b7e4c6771f409f92c178c3cbc0
bedag/hello-data-dc-portal:1.7.0-dev-SNAPSHOTsha256:dbd735d0922b1f15bb9e6dd26cf15b0447bc970a7bb0356f20ede436c448ceff
bedag/hello-data-dc-postgres:1.7.0-dev-SNAPSHOTsha256:a45793378d116dc785f95b8cdef4b52611221d21e247fc46877a1a9f5eed794f
bedag/hello-data-dc-superset:1.7.0-dev-SNAPSHOTsha256:24c3bec6ce6ca6c19b321abb4092246257e5d4d79a5e23b23927dc2332e8db01
bedag/hello-data-portal-api:1.7.0-dev-SNAPSHOTsha256:3c04760623551bee0ebc1f94c7a8e4862c181d5addb7ea807d72ad3e834cbde5
bedag/hello-data-showcase:1.7.0-dev-SNAPSHOTsha256:fccf82b7a1607d66bed86af1500e74ee20f07b9d689efa05ce107d44a436c960
bedag/hello-data-sidecar-airflow:1.7.0-dev-SNAPSHOTsha256:1757c8032837ff0e6d8bd7b3d902f671c646cd177af448ddfa1db1ab09af7643
bedag/hello-data-sidecar-airflow:airflow3-1.7.0-dev-SNAPSHOTsha256:e4e086c3cf8087afb7fa619eec91cbf7bdd8ccd83bc39dc4811bd4f965be6e4a
bedag/hello-data-sidecar-cloudbeaver:1.7.0-dev-SNAPSHOTsha256:43415c12ca75b5d4a13e606362aed81618116fea6f79971329237515c01fb8da
bedag/hello-data-sidecar-dbt-docs:1.7.0-dev-SNAPSHOTsha256:8eb27f1e1bf0b08e06c51efed6b5d9df1ba228374d93f92ada4fed3ca7f4b4f6
bedag/hello-data-sidecar-portal:1.7.0-dev-SNAPSHOTsha256:bb9df100b7fc16cf33fa896562dc237d8dc3eb89c06b41ec4ba56d9a121c0f35
bedag/hello-data-sidecar-sftpgo:1.7.0-dev-SNAPSHOTsha256:e1b8f86a646062baaefed564f9cea2fcbc744a0d42ddfd1619a3a8554beb8e5d
bedag/hello-data-sidecar-superset:1.7.0-dev-SNAPSHOTsha256:d1be915120bcecf6df1f257ef3ed5128a4bc581357000db1aed0b57154922c8c
bitnamilegacy/minio-client:latestsha256:00dcc4e58ada0df45bb7d9ee435af98295f96c27c3c68292ce78ec700a87b511
bitnamilegacy/minio:latestsha256:451fe6858cb770cc9d0e77ba811ce287420f781c7c1b806a386f6896471a349c
drakkan/sftpgosha256:1edd28d80de2a008863fbfc58c8ff7db47b1b410bae48d4e6076192337809b11
nats:alpine3.20sha256:73b0ba5fec5518c5f698597c58d2a3350a2b5ccae43e84c308f8d2da1242deca
redis:latestsha256:1f88291b4c57bdf249f02eb085a8669889b2d2954e91d4de5118a5da6b78dd53
rnwood/smtp4dev:v3sha256:211a60c1a4f51ff7ace4a35de055797348994b0e84ab36734991235f90f9ac75