<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=24780) </details> <!--IssueSummary end--> # 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](https://testing.googleblog.com/2011/09/10-minute-test-plan.html) and [this wiki page from an open-source tool that implements the ACC model](https://code.google.com/archive/p/test-analytics/wikis/AccExplained.wiki). ## 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. * Git is * Secure * Git logs for new commits show the "noreply" email address. * Repository is * Secure * Views app-wide show the "noreply" email address. * Admin is * Intuitive * The "noreply" email domain can be configured. ## 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 1. Assign "noreply" commit email address. 1. Add a file via the web UI to create a commit. 1. Pull and check git logs for the "noreply" email address. [Test Coverage sheet](https://docs.google.com/spreadsheets/d/1RlLfXGboJmNVIPP9jgFV5sXIACGfdcFq1tKd7xnlb74/)