1 Evaluation of Testing Software for Symbian OS/C++ and Series60 Jutta Jokela

2 The Project Series 60 phones using C++  Testing software coverage  Automation testing possibilities  Testing software capabilities

3 Symbian OS For devices with low memory and power consumption Most used in smart phones Phones in the market do not yet have all the functionalities that could be included Physical aspects differ

4 Symbian as a Testing Environment Challenging because end devices are not compatible (e.g. Series 60 vs. UIQ) Core C++ basis can make testing very basic  More manual testing used Public testing software range very limited

5 Parts Testing software  Digia AppTest  Mobile Innovation TRY Applications  Console application - Hercules  GUI application – Shoppinglist SDK  SDK 2.0 supporting CodeWarrior for Digia AppTest  SDK 2.1 supporting Visual Studio C++.NET for TRY IDE  CodeWarrior for Digia AppTest  Visual C for Mobile Innovation TRY

6 Testing Software Digia AppTest Mobile Innovation TRY NTS Penrillian SymbianOSUnit TestWell

7 Applications - Console application - Hercules Will be delivered with Jo Stichbury’s book (Symbian OS Explained) Basic features:  Client calls for a heroic deed from the server where heroic deeds are as methods  Some random heroic deed is caught  The deed is sent back to client Test HerculesClientServer

8 Applications - GUI Application - Shoppinglist Delivered with Nokia SDK Basic features:  The user can add, mark and delete items to the shoppinglist

9 Test cases Built on repeatability basis All the basic features tested Extreme conditions - memory Display Code tests

10 Mobile Innovation TRY BASIC used as scripting language Application should have GUI Consists of an editor and application engine Logs written real time Application testing accomplished by recording key strokes

11 TRY Example

12 Digia AppTest Part of Digia QualityKit XML Does not include editor Logs XML-formed Graphical representation of the results possible Scripts written manually or by recording Extensive help

13 Digia AppTest

14 Testing results – TRY Test automation easy  Repeatability easily structured Running the script can be interfered Screenshots can be taken Debugging the script possible Memory amount can be changed within a script

15 Errors - TRY Buttons are shown as binary code Closing application too soon, crashes the emulator Sometimes case sensitive Unclear which program is foreground and background Chinese scripting created when building the config.try script Empty log created every time TRY is started No real help

16 Testing results – Digia AppTest Test automation easy Should support console applications also Memory allocation requires own DLL Screenshots can be taken and compared Logs are formed automatically

17 Conclusions TRY is good tool for basic developers Digia QualityKit can be used in more advanced ways More software coming to mass market