These delivery tests are interim test widgets for delivery purposes only, and exercise the BONDI 1.1 CR APIs.

The test widgets are delivered with the WRT delivery.

See also:

• Test results for M2.3
• m2.3 bugs
• Acceptance tests for the previous M2.2 milestone

The tests are organised as a single widget for each API group.

1. appconfig.wgt

This exercises the appconfig API by setting and then reading back the time from appconfig.

• Install and launch the appconfig test widget
• Pressing the button to set and read back the time
• The test passes if a date string is printed

2. applauncher.wgt

The test relies on a ‘com.aplixcorp.test’ ‘Hello World Sample’ application that must be installed beforehand as the README instructs.

• Install the com.aplixcorp.test application
• Install and launch the applauncher test widget
• Click the top most testLaunchApplication button
• The test basses if the test application launches and displays its ‘Hello World Sample’ title

3. filesystem.wgt

The “Web commander” widget is used verify filesystem support.

• Install and launch the filesystem test widget
• Test passes if the widget launches and lists the /tmp directory and it is possible to navigate around the filesystem

4. geolocation.wgt

The geolocation widget tests acquisition of location from the location framework. On a terminal this requires the LBS driver to be working and for there to be a working GPS signal. On the Coronado simulator it requires the LBS service emulation to be running.

• Install and launch the geolocation test widget
• Test getCurrentLocation passes if a current position is printed
• Click the “test startWatchPosition” button to activate a watch
• Test passes if position updates are printed
• Finally click “test stopWatchPosition” to clear the watch

5. contact.wgt

The contact test widget exercises a simple sequence of operations to create, add, update and delete contacts.

• Install and launch the contact test widget
• Click test createContact button
• Test passes if it prints “created contact”
• Click test addContact button
• Test passes if it prints “added contact successfully”
• Click test updateContact button
• Test passes if it prints “updated contact successfully”
• Click test deleteContact button
• Test passes if it prints “deleted contact successfully”

6. messaging.wgt

The messaging test widget tests creation and sending of messages via SMS only. This only works on a terminal, and requires a working SIM to be present. The destination number for the test SMS is hard-coded in the widget itself, so it is necessary to edit the widget to configure the number of a phone that is available locally.

• Edit the messaging test widget with your own (destination) test number
• Repackage (i.e. freshen), install and launch the test widget
• Click the button to send the test message
• The test passes if the recipient receives a text message

7. commlog.wgt

The commlog test widget retrieves the current state of the SMS inbox. For the test to be useful, there need to be one or more stored messages on the terminal. If necessary, insert a working SIM and send one or more SMS text messages with recognisable body text from any other phone to the test SIM.

• Install and launch the commlog test widget
• Click the button to getSMSLog
• If the widget retrieves the body of the messages successfully, the test passes