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
Review product requirements and designs to identify risk and steer the team on quality strategy.
Review code in collaboration with counterpart teams to ensure adequate test coverage is present.
Partner with all development teams to ensure that testability is built in.
Be a champion for better software design, promote proper testing practices and bug prevention strategies.
Timely feedback loop
Use the data from test results to improve test gaps in our test suites.
Conduct test gap analysis from bugs that are filed by GitLab users.
Be a sounding-board for our end users and non-engineering stakeholders by integrating their feedback on quality into the development process.
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.