diff options
| author | Marco Miller <marco.miller@ericsson.com> | 2020-09-04 12:51:36 -0400 |
|---|---|---|
| committer | Marco Miller <marco.miller@ericsson.com> | 2020-09-04 12:51:39 -0400 |
| commit | c044885ac78156eb9ddc3bf00500f366ba4d39d1 (patch) | |
| tree | 67055f2f926e85f3c45af38e65fffe45e7948d10 | |
| parent | eb767fff4a820d32eec7971af015f0c2044c79e1 (diff) | |
e2e-tests: Add rename-project to the plugins list
As that plugin is now also relying on this framework from core Gerrit.
Change-Id: I3cbba66564a9ccfee97395396143764e26a491a7
| -rw-r--r-- | Documentation/dev-e2e-tests.txt | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/dev-e2e-tests.txt b/Documentation/dev-e2e-tests.txt index ccd83e442d..6ee22bde39 100644 --- a/Documentation/dev-e2e-tests.txt +++ b/Documentation/dev-e2e-tests.txt @@ -180,9 +180,11 @@ time. Plugin or otherwise non-core scenarios may do so just as well. The core java package `com.google.gerrit.scenarios` from the example above has to be replaced with the one under which those scenario classes are. Such extending scenarios can also add extension-specific properties. -Early examples of this can be found in the Gerrit -`link:https://gerrit.googlesource.com/plugins/high-availability[high-availability]` and -`link:https://gerrit.googlesource.com/plugins/multi-site[multi-site]` plugins test code. +Examples of this can be found in these Gerrit plugins test code: + +* `link:https://gerrit.googlesource.com/plugins/high-availability[high-availability]` +* `link:https://gerrit.googlesource.com/plugins/multi-site[multi-site]` +* `link:https://gerrit.googlesource.com/plugins/rename-project[rename-project]` Further above, the `_PROJECT` keyword is prefixed with an underscore, which means that its value gets automatically generated by the scenario. Any property setting for it is therefore not |