📝 Update docs

Author: opacam

doc/source/testing_pull_requests.rst

@@ -103,30 +103,31 @@ Using python-for-android commands directly from the pull request files
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 - Enter inside the directory of the cloned repository in the above
-  step and run p4a command with proper args, eg::
+  step and run p4a command with proper args, eg (to test an modified
+  `pycryptodome` recipe)::
 
     .. codeblock:: bash
 
         cd p4a-feature-fix-numpy
         PYTHONPATH=. python3 -m pythonforandroid.toolchain apk \
-            --private=testapps/testapp_sqlite_openssl \
-            --dist-name=dist_test_app_python3_libs \
+            --private=testapps/on_device_unit_tests/test_app \
+            --dist-name=dist_test_app_unittests_pycryptodome \
             --package=org.kivy \
-            --name=test_app_python3_sqlite_openssl \
+            --name=test_app_unittests_pycryptodome \
             --version=0.1 \
-            --requirements=requests,peewee,sdl2,pyjnius,kivy,python3 \
+            --requirements=sdl2,pyjnius,kivy,python3,pycryptodome \
             --ndk-dir=/media/DEVEL/Android/android-ndk-r20 \
             --sdk-dir=/media/DEVEL/Android/android-sdk-linux \
             --android-api=27 \
             --arch=arm64-v8a \
-            --permission=INTERNET \
+            --permission=VIBRATE \
             --debug
 
 Things that you should know:
 
 
-    - The example above will build an testapp we will make use of the files of
-      the testapp named `testapp_sqlite_openssl.py` but we don't use the setup
+    - The example above will build an test app we will make use of the files of
+      the `on device unit tests` test app but we don't use the setup
       file to build it so we must tell python-for-android what we want via
       arguments
     - be sure to at least edit the following arguments when running the above
@@ -159,19 +160,19 @@ Installing python-for-android using the github's branch of the pull request
         cd p4a-feature-fix-numpy
         pip3 install . --upgrade --user
 
-- Now, go inside the `testapps` directory (we assume that you still are inside
-  the cloned repository)::
+- Now, go inside the `testapps/on_device_unit_tests` directory (we assume that
+  you still are inside the cloned repository)::
 
     .. codeblock:: bash
 
-        cd testapps
+        cd testapps/on_device_unit_tests
 
 - Run the build of the apk via the freshly installed copy of python-for-android
   by running a similar command than below::
 
     .. code-block:: bash
 
-        python3 setup_testapp_python3_sqlite_openssl.py apk \
+        python3 setup_test_app.py apk \
             --ndk-dir=/media/DEVEL/Android/android-ndk-r20 \
             --sdk-dir=/media/DEVEL/Android/android-sdk-linux \
             --android-api=27 \
@@ -182,8 +183,7 @@ Installing python-for-android using the github's branch of the pull request
 Things that you should know:
 
     - In the example above, we override some variables that are set in
-      `setup_testapp_python3_sqlite_openssl.py`, you could also override them
-      by editing this file
+      `setup_test_app.py`, you could also override them by editing this file
     - be sure to at least edit the following arguments when running the above
       command, since the default set in there it's unlikely that match your
       installation:

testapps/on_device_unit_tests/README.rst

@@ -4,18 +4,38 @@ On device unit tests
 This test app runs a set of unit tests, to help confirm that the
 python-for-android build is actually working properly.
 
+Also its dynamic, because it will run one app or another depending on the
+supplied recipes at build time.
+
+It currently supports three app `modes`:
+  - `kivy app` (with sdl2 bootstrap): if kivy in recipes
+  - `flask app` (with webview bootstrap): if flask in recipes
+  - `no gui`: if neither of above cases is taken
+
 The main tests are for the recipes built in the apk. Each module (or
 other tool) is at least imported and subject to some basic check.
 
-This app is experimental, it doesn't yet support things like testing
-only the requirements you ask for (so if you build with requirements
-other than those specified, the tests may fail). It also has no gui
-yet, the results must be checked via logcat.
+This test app can be build via `setup_test_app.py` or via buildozer. In both
+cases it will build a basic kivy app with a set of tests defined via the
+`requirements` keyword (specified at build time).
+
+In case that you build the `test app with no-gui`, the unittests results must
+be checked via command `adb logcat` or some logging apk (you may need root
+permissions in your device to use such app).
+
+Building the app with python-for-android
+========================================
+
+You can use the provided file `setup_test_app.py`. Check our `Makefile
+<https://github.com/kivy/python-for-android/blob/develop/Makefile>`__ to guess
+how to build th e test app, or also you can look at `testing pull requests documentation
+<https://github.com/kivy/python-for-android/blob/develop/doc/source/testing_pull_requests.rst>`__,
+which describes some of the methods that you can use to build the test app.
 
-Building the app
-================
+Building the app with buildozer
+===============================
 
-This app should be built using buildozer, which it also serves as a
+This app can be built using buildozer, which it also serves as a
 test for::
 
   $ buildozer android debug