supportive documents are:

• scope Base 3 PoC
• excel overview of asset list

Objective: Overview of status of all (grouped) pipelines including test pipelines on DLV

What: Main page - Overview of high level groups, per group the high level result is displayed with a green or orange or red indication Detailed page per group - When clicked on a group: overview of all release pipelines and test pipelines belonging to this group, per asset (pipeline) or test pipeline the result and date/time run Detailed page per release pipeline or test pipeline - When clicked on a pipeline: detailed information this pipeline (what? number of tests run?)

Where: Run Information of all pipelines (for NextensNL and Nextens LNRS) is exported to PowerBI, where it is collected and grouped, the display of the dashboard is made visible as an external page in Azure DevOps (to be investigated) Phase 1: Dashboard in DevOps only, PoC for Base 3 Phase 2: Dashboard via PowerBI

How: Preparation

• Determine which high level groups [Daan/Dirk] [1st draft delivered]
• Determine which assets belongs to which group [Daan/Dirk] [1st draft delivered]
• Determine which pipelines are linked to which assets [Richard]
• Determine which pipelines contains which auomated tests (Unit, API, UI) [Richard]
• Determine which automated tests are not yet part of pipeline [Richard]
• Determine how to hanlde automated tests not yet part of a pipeline [Richard]
• Determine if automated tests part of a pipeline should also be made available in a test pipeline (to be able to run them on request) [Richard]
• Investigate how data can be exported to PowerBI [Salima]

Set up

• Add available test automation to pipelines (either asset pipeline or create separate test pipelines) [Applicable teams, supported by TA engineer support]
• Determine which test pipelines belongs to which group [Daan/Dirk]

Creation

• Collect per pipeline the required information (for NextensNL and Nextens LNRS)
• Export data to PowerBI
• Group assets/pipelines and test pipelines
• Create dashboard with main page and detailed page per group
• Make pages available in Azure DevOps

Assumptions:

• Each asset is covered by a (build/release) pipeline
• Each pipeline contains unit tests
• All automated tests are available in pipelines
  • Available API and UI tests 1:1 linked to an asset is part of the asset pipeline
  • Automated tests linked to > 1 asset should is available in a test pipeline
• A high level group contains 1 or more asset pipelines and 0, 1 or more test pipelines