WIP: Test plan for "Keep Personal Email Private"
Test Plan
Introduction
This test plan is for https://gitlab.com/gitlab-org/gitlab-ce/issues/43521. The feature allows a user to be assigned a "noreply" email address to be used as their commit email when performing web-based actions.
Scope
- Assignment of the commit email address, not its display (i.e., the email address will still be displayed anywhere it currently would)
- Applies to new commits, not historical data or imports
ACC Matrix
Secure | Responsive | Inituitive | Reliable | |
---|---|---|---|---|
Git | ||||
Settings | ||||
Repository | ||||
Admin |
For more information see the Google Testing Blog article about the 10 minute test plan and this wiki page from an open-source tool that implements the ACC model.
Capabilities
-
Settings are
- Intuitive
- A "noreply" commit email can be assigned with minimal actions.
- There is guidance to inform users who aren't aware of the feature.
- Intuitive
-
Git is
- Secure
- Git logs for new commits show the "noreply" email address.
- Secure
-
Repository is
- Secure
- Views app-wide show the "noreply" email address.
- Secure
-
Admin is
- Intuitive
- The "noreply" email domain can be configured.
- Intuitive
Test Plan
It's likely that verification of assignment and display of commit email addresses in the UI can be covered at the unit/integration level. It might also be worthwhile verifying git logs directly in an end-to-end test.
Automated end-to-end tests:
Scenario 1: Git logs and web views
- Assign "noreply" commit email address.
- Add a file via the web UI to create a commit.
- Pull and check git logs for the "noreply" email address.
Edited by Mark Lapierre