Test Governance Group

Common Links

Mission

Ensure highly effective testing across all teams by providing test frameworks and tools, optimizing configurations, and partnering with development teams to create and maintain comprehensive functional tests that prevent bugs from reaching customers.

Vision

• Providing stable, repeatable, and fast test frameworks and configurations to catch bugs as early as possible
• Training to upskill teams on functional testing and quality. Every engineering team should know what to test, when, and how to contribute valuable tests to our test suites to maintain test coverage as the application grows
• Incident and bug analysis for GitLab.com and Dedicated - identifying test gaps and working with development teams to improve testing
• Effective quarantine process to quickly identify and isolate flaky tests for stage groups to fix or remove

Team members

Name	Role
Nadya Denisenko	Manager, Engineering
Chloe Liu	Staff Software Engineer in Test, Development Analytics
Désirée Chevalier	Senior Software Engineer in Test, Test Governance
Jay McCure	Senior Software Engineer in Test, Dev:Create
Joy Roodnick	Software Engineer in Test, Test Governance
Tiffany Rea	Senior Software Engineer in Test, CI:Verify
Tim Beauchamp	Software Engineer in Test, Test Governance
Will Meek	Senior Software Engineer in Test, Test Governance

Core Responsibilities

graph LR
    A[Test Governance Team]

    A --> B[Provide test expertise for critical Product releases]
    B --> B1[Define test strategy for the critical feature releases]
    B --> B2[Ensure adequate and robust test coverage for critical features]
    B --> B3[Stay informed about the stage roadmap]

    A --> C[Stage-level test tools and infrastructure]
    C --> C1[Design, Build and continuously improve tests, test frameworks and tools]
    C --> C2[Influence, advise and increase the testing capabilities for product teams]
    C --> C3[Monitor and address test flakiness]

    A --> D[Test guidance. Provide guidance and coach engineering teams in the areas:]
    D --> D1[Writing e2e tests and feature specs]
    D --> D2[Debugging and fixing test failures]
    D --> D3[Planning testing early in the development process]
    D --> D4[Anticipating test infrastructure needs and requesting change in advance]
    D --> D5[Shift left and maintaining appropriate ratio between unit, integration and e2e tests]
    D --> D7[Post-incident action]

    A --> E[E2E Pipeline triage. Shared responsibility among all DevX sub-department]

Working with us through request for help

The Test Governance group aims to better enable teams to apply the principle that quality is everyone’s responsibility. Please request all support via the RFH process below. This will allow us to prioritize requests against our planned project roadmap. Please use the following Request for Help process for all support requests.

Request for Help Process

1. Creates an issue in the Request for Help project. Please complete all sections of the template so we can quickly triage your request
2. The Test Governance team will triage the request within a week, adding appropriate labels and assigning team members based on the request type and priority. You will recieve details about the prioritization and next steps on the request for help issue.

For more detailed guidance on E2E test coverage, consider these approaches:

• Engage with key DRIs to define persona use cases that illustrate how different customers will use new features
• Evaluate which parts of use cases can be covered by lower-level tests versus E2E tests, keeping the entire testing pyramid in mind
• Refer to our documentation on Testing Best Practices before submitting your request

View page source - Edit this page - please contribute.