Update of "Test and debug strategies on AndroWish"
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview

Artifact ID: 8de8d3065bbd4b22fb297f224374a9370f62a59d
Page Name:Test and debug strategies on AndroWish
Date: 2019-04-26 07:16:44
Original User: chw
Parent: 897fd5ef2a9c2f4038e393c4f6863cba16fdf7ec
Content

Test and debug strategies on AndroWish

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 (adb) should be used on a development system. Refer to the description of the 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 borg log ... command or the sdltk log ... command can be used.

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