Consolidate Testing Categories
Overview
Upon taking over Verify:Testing, I realized a significant overlap in the JTBDs, markets, and purposes of the Testing Categories. A few of which have no planned developments and have very minimal offerings. This lack of focus in our Testing depth dilutes the capabilities we offer by trying to cover as much ground as possible with MVCs instead of focusing on the problems we need to solve for the market and users.
Proposal
- Move Accessibility Testing scope to Code Testing Testing and dissolve the Accessibility Testing category.
- Combine Usability Testing into Review Apps.
Moving Accessibility Testing to Performance Testing
A key piece of Code Testing is to see how changes impact the application and if the changes exceed standards for quality. This can be from a web, UI, or API level. Accessibility Testing is about previewing changes in order to make sure the changes are meeting standards for accessibility. Both feature sets leverage reports and code changes to test against preset thresholds and users should be able to consume the impacts of changes in both lenses.
Combine Usability Testing into Review Apps
Review Apps actually deliver on the core purposes of Usability Testing such as previewing changes before production. Usability Testing is only composed of the Visual Review Tool, which is actually very similar to a Review App in the MR. When we dissolve Usability Testing we would be moving Visual Review Tool under Review Apps. A core JTBD for Usability is to Gather Usability Feedback which is done by previewing the changes in a Review App and leaving comments in merge requests.
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
Chief Product Officer @sfwgitlab -
VP of Product @adawar -
The Product Director relevant to the stage group(s) @kencjohnston -
The Engineering Director relevant to the stage group(s) @sgoldstein -
Director of Product Design @vkarnes -
CEO
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @edjdev
-
Vice President of Development @clefelhocz1
-
Vice President of Quality @meks
-
Vice President of User Experience @clenneville
-
The Product Marketing Manager relevant to the stage group(s) -
Senior Manager, Technical Writing @susantacker
After Approvals and Merge
-
Create an issue in the triage-ops project to update GitLab Bot automation -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels