The features in the Verify stage help users keep strict quality standards for production code by using automated testing and reporting. Delivery teams rely on the foundation provided by this stage as they fully embrace continuous development that automates builds, integration, and verification of their code while accelerating their team's velocity. Testing ranges from unit testing, load testing, all the way to accessibility and usability testing.
The Verify UX team is part of the CI/CD UX team. Our goal is to empower our customers by streamlining, expanding, and enabling increasingly complex configurations. We do so by providing the best management experience when setting up, configuring, or troubleshooting pipelines. Our design mission is to bring to the forefront simple ways to make GitLab the tool of choice for continuous integration users.
We are committed to staying aligned on shared UX with the engineering groups as much as possible, and being the conversation drivers with product managers and other counterparts. The Verify UX team is working together to uncover customers' core needs and streamlining their workflow. Visit CI/CD UX page to read about the department's high-level strategy.
We have different user types we consider in our experience design effort. Even when a user has the same title, their responsibilities may vary by organization size, department, organization structure, and role. Here are some of the people we are serving:
A Job to be Done (JTBD) is a framework, or lens, for viewing products and solutions in terms of the jobs customers are trying to achieve.
We divided the Verify stage into dedicated experience groups to align with a similar split undertaken by our engineering and PM counterparts. To deliver seamless user experiences, we share responsibility in the overall vision, goals, and research initiatives related to overlapping features. The UX teams work closely together and have shared coverage in the following areas: