Documentation: Refactor to match other plugin documentation
Move in-tree testing section before eclipse-related section for
consistency across other plugins and also to match standalone case.
Change-Id: Iea385057a9e2e4e91c65aff2056640c6cf1ea3fe
diff --git a/src/main/resources/Documentation/build.md b/src/main/resources/Documentation/build.md
index 91cc37a..1d86dd0 100644
--- a/src/main/resources/Documentation/build.md
+++ b/src/main/resources/Documentation/build.md
@@ -71,6 +71,13 @@
bazel-bin/plugins/@PLUGIN@/@PLUGIN@.jar
```
+To execute the tests run either one of:
+
+```
+ bazel test --test_tag_filters=@PLUGIN@ //...
+ bazel test plugins/@PLUGIN@:@PLUGIN@_tests
+```
+
This project can be imported into the Eclipse IDE:
Add the plugin name to the `CUSTOM_PLUGINS` and to the
`CUSTOM_PLUGINS_TEST_DEPS` set in Gerrit core in
@@ -80,13 +87,6 @@
./tools/eclipse/project.py
```
-To execute the tests run either one of:
-
-```
- bazel test --test_tag_filters=@PLUGIN@ //...
- bazel test plugins/@PLUGIN@:@PLUGIN@_tests
-```
-
How to build the Gerrit Plugin API is described in the [Gerrit
documentation](../../../Documentation/dev-bazel.html#_extension_and_plugin_api_jar_files).