Acceptance and Usability/Accessibility Testing Improvements
This issue represents a 2019 product vision deliverable. At the moment this is a placeholder and will soon be expanded to include more specifics about what we want to implement.
GitLab has lots of capability for testing various aspects of software, but most are aimed around functional testing of code.
Usability testing is a technique used in user-centered interaction design to evaluate a product by testing it on users. This can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system. It's slightly different than UAT in that the primary purpose of a usability test is to improve a design, rather than to accept/reject a deployment.
User acceptance testing (UAT) is a form of testing with end users or people representing end-users so that software is tested in the "real world". This includes beta testing or testing with any subset of the intended audience. For GitLab, this could involve exposing Review Apps to an end-user audience, but more often it involves a form of staging deployment that is accessed by end-users before deployment to the full production environment.
- Usability and UAT are similar
- Accessibility is a legal requirement for many applications
- Accessibility as a primary concern is the right thing to do
- There are great frameworks for it like https://github.com/paypal/AATT
(Include use cases, benefits, and/or goals)
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)