Add release check for benchmark

getodk · Aug 16, 2024 · 7e17905 · 7e17905
1 parent d4701a0
commit 7e17905
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/README.md b/README.md
@@ -262,6 +262,7 @@ Maintainers keep a folder with a clean checkout of the code and use [jenv.be](ht
 - make sure CI is green for the chosen commit
 - run `./gradlew releaseCheck`. If successful, a signed release will be at `collect_app/build/outputs/apk` (with an old version name)
 - verify a basic "happy path": scan a QR code to configure a new project, get a blank form, fill it, open the form map (confirms that the Google Maps key is correct), send form
+- run `./benchmark.sh` with a real device connected to verify performance
 - verify new APK can be installed as update to previous version and that above "happy path" works in that case also
 - create and publish scheduled forum post with release description
 - write Play Store release notes, include link to forum post

diff --git a/benchmark.sh b/benchmark.sh
@@ -0,0 +1 @@
+./gradlew collect_app:connectedAndroidTest -Pandroid.testInstrumentationRunnerArguments.package=org.odk.collect.android.benchmark