Artifact 8de8d3065bbd4b22fb297f224374a9370f62a59d:

D 2019-04-26T07:16:44.364
L Test\sand\sdebug\sstrategies\son\sAndroWish
P 897fd5ef2a9c2f4038e393c4f6863cba16fdf7ec
U chw
W 1097
<h2>Test and debug strategies on AndroWish</h2>

For interactive testing, follow the directions given in [tkconclient].

When scripts are not run interactively but started using e.g. an icon on the Android home screen, script errors may show up in the Android system log buffer when not reported through the Tcl background error mechanism. In this case, the Android Debug Bridge ([https://developer.android.com/studio/command-line/adb|adb]) should be used on a development system. Refer to the description of the [https://developer.android.com/studio/command-line/logcat|logcat command-line tool] and see an example output in the last image of the [AndroWish SDK] documentation.

Similarly, when explicit log output shall be written by application code, the <tt>[Android facilities|borg log] ...</tt> command or the <tt>[sdltk command|sdltk log] ...</tt> command can be used.

Output to the <tt>stderr</tt> and <tt>stdout</tt> channels in non-interactive scripts is normally not shown, but can be easily displayed, too, when the console window is made viewable using <tt>console show</tt>.
Z a189102aef58b768fc8abe6e293583b9