Test that submit rule is not invoked too often when getting/querying change

These tests verify that submit rules are not invoked too often. They are
added to prevent regressions. Before change I6863f764d in Gerrit core
submit rules were invoked too often:

1. when getting change details submit rules were invoked twice instead
   of just once, once for populating submit requirements in the change
   JSON and once for checking if the submit button should be visible.

2. when querying a change submit rules were invoked to check if the
   submit button should be visible, but it's expected that submit rules
   are not invoked at all

The issue only occurred if the list changes options ALL_REVISIONS and
CURRENT_ACTIONS were used together.

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