Adapt test for adding multiple reviewers to change in Gerrit core

When multiple reviewers are added at once via the PostReview REST
endpoint Gerrit used to send out one event per newly added reviewer, but
now it sends out only one event which contains all newly added
reviewers.

The code-owners plugin listens to the add reviewer event to add a change
message that lists the paths that are owned by the new reviewers. Since
such an event was triggered for each of the newly added reviewers so
far, we ended up with one change message per reviewer. Now, with only
one batch event being sent out, we have only one change message that
lists the owned paths for all newly added reviewers.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I1469d3cf69d7d23107b3962006f5df9377edb153
1 file changed
tree: e4c3b2038ae4555a2bc63361a585992add7cd7e8
  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.