The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
GitLab's testing focus is mainly around the functional testing of code in software. We are interested in expanding our testing capabilities to include user-centered interaction evaluation. With the vision of Usability Testing, GitLab is embedding direct input on how real users use the system within your testing practice.
Usability testing is slightly different from user acceptance testing (UAT) in that the primary purpose of a usability test is to improve a design, rather than a gate to approve a deployment. At GitLab, we're believers in user-focused design without manual interference. Usability Testing's vision is meant to celebrate the designer and product manager as first-class parties in the development lifecycle. By adding features with them in mind, we can help them to contribute their best.
A related category geared toward the readability of your applications is Accessibility Testing. As an end to end application, we offer other features involving the designer in the DevOps lifecycle, including Design Management in the Create stage.
Interested in joining the conversation for this category? Please join us in the category's issues where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
This page is maintained by the Product Manager for Testing, James Heimbuck (E-mail)
The next thing we are working on for Usability Testing is &3085 which will bring the ability to take and attach screenshots to comments from the Visual Review tool. This will help users simplify their workflow and not have to take a screenshot and attach it to the comment after it is created in the MR. This also allows users without an account or an account without permissions to add those screenshots which they cannot do today.
This category is currently at the "Minimal" maturity level, and our next maturity target is Viable (see our definitions of maturity levels). Key deliverables to achieve this are:
We may find in research that only some of these issues are needed to move the vision for this category forward.
Usability testing is a feature offered primarily through integrations by competitive products. Taking advantage of Review Apps, we're able to offer a much nicer experience with a manual review tool for Review Apps via gitlab-org&960 where feedback can be requested on a review environment. This brings feedback much earlier into the development process and integrates that automatically with GitLab Merge Requests.
Marker.io is a product that ships mostly as an extension to go into your browser and allows you to raise an issue with various issue providers (Trello, JIRA, GitHub and even GitLab). It provides a very intuitive user interface for screenshots, annotations and other discussions.
Netlify recently introduced new functionality to Deploy Previews that allows users to annotate, take screenshots and leave comments on a deploy preview. This alongside their integrations with various project management tools is another step towards allowing the non developer personas to push their feedback further left in the development cycle to speed up the feedback loop.
The most popular issue for the category is gitlab#27228 which adds image annotations for the Visual Review tool.
An interesting use case we first heard about from a customer is designers wanting to see their previous comments for unresolved threads in the tool (gitlab#325454). We think this is an interesting and powerful way product designers and product managers can engage with the Usability Category and more quickly give feedback to the developers they work with to deliver customer value.
For usability testing, our internal team has asked for built-in support for visual regression testing (gitlab#26489).
When we think about the long term vision of the Usability category we see opportunities to build in support for visual regression testing to help developers see visual degradations before they merge.