SkQP Documentation
No-Try: true
Change-Id: Id32e909544286eed701a1db8f0913a883af4215f
Reviewed-on: https://skia-review.googlesource.com/c/196380
Reviewed-by: Hal Canary <halcanary@google.com>
Commit-Queue: Hal Canary <halcanary@google.com>
diff --git a/site/dev/testing/skqp.md b/site/dev/testing/skqp.md
index 791fb8f..2c6dae7 100644
--- a/site/dev/testing/skqp.md
+++ b/site/dev/testing/skqp.md
@@ -11,6 +11,9 @@
The listing can be found here:
[https://storage.googleapis.com/skia-skqp/apklist](https://storage.googleapis.com/skia-skqp/apklist)
+If you are looking at Android CTS failures, use the most recent commit on the
+`origin/skqp/release` branch.
+
To run tests:
adb install -r skqp-universal-{APK_SHA_HERE}.apk
@@ -24,14 +27,22 @@
Note the test's output path on the device. It will look something like this:
01-23 15:22:12.688 27158 27173 I org.skia.skqp:
- output written to "/storage/emulated/0/Android/data/org.skia.skqp/files/output"
+ output written to "/storage/emulated/0/Android/data/org.skia.skqp/files/skqp_report_2019-02-28T102058"
Retrieve and view the report with:
- OUTPUT_LOCATION="/storage/emulated/0/Android/data/org.skia.skqp/files/output"
- adb pull $OUTPUT_LOCATION /tmp/
+ OUTPUT_LOCATION="/storage/emulated/0/Android/data/org.skia.skqp/files/skqp_report_2019-02-28T102058"
+ adb pull "$OUTPUT_LOCATION" /tmp/
-Open the file `/tmp/output/skqp_report/report.html` .
+(Your value of `$OUTPUT_LOCATION` will differ from mine.
+
+Open the file `/tmp/output/skqp_report_2019-02-28T102058/report.html` .
+
+**Zip up that directory to attach to a bug report:**
+
+ cd /tmp
+ zip -r skqp_report_2019-02-28T102058.zip skqp_report_2019-02-28T102058
+ ls -l skqp_report_2019-02-28T102058.zip
* * *