CodeOwnerApprovalCheckTest: Make the approvedByGlobalCodeOwner more readable

Looking at the test one could think that the file was already implictly
approved by the admin user who creates the change and is a code owner.
This is not the case since implicit approvals are disabled by default.
However the test becomes more readable if we use a non-code-owner user
to create the change. Add a verification that the file is not approved
before the global code owner adds their approval. Also add some more
comments to make the code easier to read.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ib626315a1ca5efdd9b2e5a066f878507606d1ad8
1 file changed
tree: e5b9994617893d544101db9da523c0c7f873fed5
  1. java/
  2. javatests/
  3. proto/
  4. resources/
  5. test/
  6. ui/
  7. .eslintrc.json
  8. .gitignore
  9. .gitreview
  10. bower.json
  11. BUILD
  12. LICENSE
  13. package-lock.json
  14. package.json
  15. README.md
README.md

Gerrit Code Review code-owners plugin

This plugin provides support for defining code owners for files in a repository.

If the code-owners plugin is enabled, changes can only be submitted if all touched files are covered by approvals from code owners.

Also see resources/Documentation/about.md

IMPORTANT: Before installing/enabling the plugin follow the instructions from the setup guide, see resources/Documentation/setup-guide.md