Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Quality Department

On this page

Child Pages

On-boarding

Guidelines

Test Engineering
Triage Operations

Project Management

Roadmap

Vision

Ensure that GitLab consistently releases high-quality software across the growing suite of products, developing software at scale without sacrificing quality, stability or velocity. The quality of the product is our collective responsibility. The quality department makes sure everyone is aware of what the quality of the product is, empirically.

To execute on this, we categorize our vision into the following areas.

Culture of Quality

Champion an early culture of quality in the development process

Timely feedback loop

Test Coverage

Test framework reliability and efficiency

Improve test coverage

Self-managed usecase

Improve Quality in release process

Engineering Productivity

Quality Engineering Teams

Dev QE team
Ops & CI/CD QE team
Secure & Enablement QE team
Engineering Productivity team

Department members

Person Role
Rémy Coutable Staff Engineer, Engineering Productivity
Mark Fletcher Engineer, Engineering Productivity
Jen-Shin Lin Engineer, Engineering Productivity
Kyle Wiebers Senior Backend Engineer, Engineering Productivity
Dan Davison Senior Test Automation Engineer, Configure
Mark Lapierre Senior Test Automation Engineer, Create:Source Code
Sanad Liaquat Senior Test Automation Engineer, Manage
Tomislav Nikić Test Automation Engineer, Create:Knowledge, Create:Editor, Gitter
Zeff Morgan Senior Test Automation Engineer, Verify
Walmyr Lima e Silva Filho Senior Test Automation Engineer, Plan
Aleksandr Soborov Test Automation Engineer, Secure
Grant Young Senior Test Automation Engineer, Enablement
Jennie Louie Test Automation Engineer, Enablement
Désirée Chevalier Test Automation Engineer, Manage

Stable counterparts

Every Test Automation Engineer is aligned with a Product Manager and is responsible for the same features their Product Manager oversees. They work alongside Product Managers and engineering at each stage of the process: planning, implementation, testing and further iterations. The area a Test Automation Engineer is responsible for is part of their title; for example, "Test Automation Engineer, Plan." as defined in the team org chart.

Every Quality Engineering Manager is aligned with an Engineering Director in the Development Department. They work at a higher level and align cross-team efforts which maps to a Development Department section. The area a Quality Engineering Manager is responsible for is part of their title; for example, "Quality Engineering Manager, Dev" as defined in the team org chart. This is with the exception of the Engineering Productivity team which is based on the span of control.

Full-stack Engineering Productivity Engineers develop features both internal and external which improves the efficiency of engineers and development processes. Their work is separate from the regular release kickoff features per areas of responsibility.

Headcount planning

We plan headcount as follows:

Failure Management Rotation

Every member in the Quality team shares the responsibility of analysing the daily QA tests against master and staging branches. More details can be seen here

Team retrospective

The Quality team holds a once-a-month asynchronous retrospective. The process is automated and notes are captured in Quality retrospectives (GITLAB ONLY)

Release process overview

Moved to release documentation.

Test Automation Framework

The GitLab test automation framework is distributed across three projects:

Architecture overview

See the GitLab QA Documentation and current architecture overview.

Installation and execution

AMA sessions

Every quarter the Quality team will host an AMA session about the testing framework. The idea is to keep everyone informed about what's new and to answer questions.

The next sessions are scheduled for 2019/09/20, 2019/12/20, and 2020/03/20.

Note: the dates mentioned above can change, but we will try to keep this document updated.