Quality Gates to ensure quality at every CI/CD step

Led UX design for the Quality Gate feature, enabling Quality Excellence teams to enforce consistent standards across the organization by creating simplified rule creation and specific test selection.

View live website Scroll to solution

Concept & Usecases

As organizations adopt automated deployments, maintaining quality at every stage becomes crucial. Poor-quality code can progress through the pipeline without proper validation mechanisms, leading to unstable releases and production issues

Transition from CI to CD:

  • Helping users to do automated deployments by checking quality rules

  • Prevent false positives/negatives from impacting promotion of code to the next stage of pipeline.
    eg: If P0/P1 test cases are passing then deploy the build

    • Maintaining Quality Standards:

  • Allowing organisations to implement uniform quality standards across teams, projects.
    eg: Fail the build and stop further deployments if new failures are present.

    •

    Research & Insights

    To build an effective solution, I conducted secondary research on existing quality gate implementations in DevOps.

    Summary

    • → Quality gates follow a CRUD workflow, allowing users to define, edit, and manage rules.
    • → Most implementations use predefined metrics (e.g., SonarQube's "code smell") to determine quality.
    • → Quality gate statuses are displayed alongside builds, showing thresholds and actual values for visibility.

    Information Architecture

    A quality gate system consists of three key components:

  • Quality Gate: A decision-making checkpoint that results in either a pass or fail.

  • Quality Profile: A collection of grouped rules that define quality standards.

  • Rule: A condition based on a metric that determines the success or failure of a build.

    •

    Final Solution

    Design Showcase

    Next Case Study

    Designing Paywalls for changing business needs

    Read case study