Test plan for "Block command line pushes if they have the user's private email address"
Introduction
This test plan is for https://gitlab.com/gitlab-org/gitlab-ce/issues/52355. The feature blocks pushes if they contain the user's private email address.
Scope
- Pushes via Git CLI client, not GitLab web UI.
- Out of scope: configuration and privacy of private email address (covered by https://gitlab.com/gitlab-org/gitlab-ce/issues/52893).
- Out of scope: pushes of someone else's private email address, e.g., via a commit another user pushed to a project that the current user forked.
ACC Matrix
Secure | Responsive | Inituitive | Reliable | |
---|---|---|---|---|
Git | ||||
Settings |
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
Git is
- Secure
- Pushes are blocked if the private email address is used.
Settings are
- Secure
- Pushes are blocked by default but the user can choose to allow them.
Test Plan
Automated end-to-end tests:
Scenario 1: Push with private email address is blocked
- Assign private commit email address and check that it is set to be blocked if included in a push.
- Configure Git CLI to use the private email address.
- Try to push.
- Check that a message reports that the push was blocked and check that the project shows that no push occurred.
Scenario 2: Push with private email address is not blocked
- Assign private commit email address but set it to allow it to be included in a push.
- Configure Git CLI to use the private email address.
- Try to push.
- Check that the push was not blocked.