Test Platform in Distribution group

Overview

The goal of this page is to document existing Quality Engineering activities in Distribution group.

Dashboards

Quality work

Quality work is being tracked in epic#9057. The epic lists large initiatives that need to be worked on to better support quality in Distribution group.

GitLab QA

GitLab QA is being used in several Distribution projects to validate that GitLab works as expected.

Project Tests type Schedule
GitLab Omnibus Full QA mirror pipeline is triggered
GitLab Charts Sanity Run automatically in merge requests and scheduled against default branch
GitLab Charts Full Triggered manually in merge requests
GitLab Operator Smoke Run automatically in merge requests
GitLab Operator Full Manually triggered
Reference Architecture Tester Full Manually triggered and FIPS QA Nightly

Check Running GitLab QA for information on how to run GitLab QA locally for development.

Investigate QA failures

  1. Search for the failure in open Pipeline Triage issue or search for the spec name in the main GitLab project
    • If Allure report is available: Click on report link -> Product defects -> Select failed spec -> click Failure issues. Demo
    • Some specs might have multiple QA failure issues with different stack trace. In such case, compare failed stack trace from the job with the ones listed in the issues.
  2. If an issue with the same error is not found

Bug Prioritization

The Distribution team works together on Bug Prioritization and aims to close at least 6 bugs per milestone based on the team’s current availability. The number of bugs per milestone is revisited in the following issue#1100.

Process:

Quad Planning

Quality team reviews open issues for quad planning following Quad Planning process.

Last modified June 27, 2024: Fix various vale errors (46417d02)