Seetest-A mobile Test Automation tool for Android, iPhone, Blackberry, Symbian & WindowsPhone 7

November 7, 2011 — anuragkhode

Guest Post By:-Tal Barmeir (CEO Experitest)

Need for Mobile Test Automation Tool on Various Platforms (Android, iPhone, Blackberry, Symbian & WindowsPhone 7) 

Since launch of the First Mobile phone in the market to the launch of hundreds of devices a month,the market has changed drastically.Unlike earlier, now:-

  • There are lots of application getting developed and launched in to the market everyday.
  • Enterprises (banks, retailers etc) need to provide access to their online services via smartphones.
  • Application developers need to quickly launch their apps on various platforms to cope up with competitive market.
  • Hardware vendors are developing many different devices based on Android and other mobile OS.
Thousands of mobile devices in the market, different OS/Platforms with different OS versions and competitive market,all these things lead to need of a comprehensive & effective automation tool which can help in  cost effective Testing of a Mobile Application or hardware they have developed in quick time.More specifically, they need a test automation tool for real physical mobile devices (not emulators) that has full coverage, ability to integrate  into their existing testing environment , is simple & quick to operate and can run the same test  on many devices/mobile OS.AND MOST IMPORTANTLY – a downloadable trial version – because there’s nothing like trying it yourself.
Well all these and many other challenges/Issues  in Mobile Application Testing will  now be addressed by an efficient Mobile Automation tool from Experitest Inc.
Experitest (www.experitest.com) – a strategic partner of both HP and Microsoft – has developed SeeTest – a test automation tool for mobile that meets all these requirements and is deployed in Fortune 500 companies worldwide, such as Microsoft, NYSE, Marvell, Texas Instruments, Clicksoftware, BSkyB, 888, Cisco and many more.  To watch a video click here

Requirement 1:  Full coverage – all smartphone OS, all functionality

All mobile OS:

  •  All types of OS:  There are 5 Android, iOS, Blackberry, WindowsPhone 7 and Symbian. To provide a real coverage of your customer base you need a tool that can test on any of these.All mobile OS versions: OS versions are constantly launched ot the market. There is need ot support all of them.
  • All mobile device models: phones, tablets. Both are used today by end users. So both need to be tested.
All functionality: Smartphones have a broad range of gestures, system alerts and many other features.  All need to be supported. Otherwise no real automation can be achieved:
  • Gestures:Swipe, drag &drop, zoom in and zoom out, mutlitouch.
  •  System alerts:Security pop ups.
  • Virtual keyboards:  all keyboard configurations
SeeTest is the most comprehensive mobile test tool today in the market. It covers all OS, all functionality. You name it, SeeTest has it.
Requirement 2:  Plug into QTP,TestComplete,MSTest,Junit,Perl,Python:-
Mobile testing is “the new guy on the neighborhood”. It is joining into a realty where organizations already have an existing testing environment such as QTP, TestComplete, MSTest, Java, Perl, Python. Naturally, organizations are looking for a solutions that can easily integrate into these existing environments so that they can continue working from their usual testing environment only extend it to cover mobile testing as well.

SeeTest has plugins into all testing environments such as QTP, Testcomplete, MSTest, JUnit, Perl and Pyhton.

Let’s take for example QTP. The SeeTest plugin enables to work from within QTP and simply create tests the regular and usual way tests are created in QTP (Keyword view, Expert view, data driven tests, test results and anaylsis), only that this time it is done on real physical mobile devices connected via a standard USB cable to the tester’s computer. The user can record/edit the test, run it and view reports – all in QTP. Just as he has always done. Same goes for all the HP testing & monitoring tools such as QC and LoadRunner.

 

Example screenshots: Keyword view, Expert view, data driven tests, test results

 

Requirement 3: simple & quick to Operate – a recorder

The mobile world changes quickly. And so should the ability to create tests easily and efficiently. The SeeTest recorder enables simple, quick test creation.

Requirement 4: Same script running on multiple devices and mobile OS.

There are 5 smartphone OS. There are hundreds of smartphone device models. There are constantly new OS versions. This reality mandates one clear and strong requirement – script once, run on any device/OS.

One of SeeTest’s main strengths is its ability to run the very same test script on any mobile OS. Any physical device. No exceptions. This brings clear and indisputable ROI to the mobile automation project.

Requirement 5: Why believe marketing materials? Try it yourself now – free downloadable trial.

Click here to download (download starts automatically)

Download a free trial here        

Watch a Video here           

Email us for a free webinar/demo/POC: support@experitest.com

_________________________________________________________________________________________________________

About Author:-

Tal Balmier is CEO of Experitest – developer of SeeTest – test automation tool for mobile that plugs into QTP,TestComplete,MSTest,JUnit,Perl,Python.


Posted in Android Application Testing, Blackberry Application Testing, Iphone Application Testing, Mobile Application Testing, Mobile application Testing and Automation tools, Symbian Application Testing, Windows Mobile Application Testing. 2 Comments »

Test Power consumption of your app with Nokia Energy Profiler

April 16, 2011 — anuragkhode

My Experience with testing mobile App & Power Usage:

I remember the day when my client had raised a bug that our application is eating too much battery (power) while using it. I was very surprised by this observation and definitely I was assigned to investigate on this issue. When I started my investigation the only thing I had in my mind was how to know that its my application only which is eating too much battery of a device. The only way I had to test it was to use the application rigorously and monitor the battery consumption or draining of battery. However it was not as easy as it was looking. I had to use another application on that device also to see that if that app is also eating battery exhaustively like ours .In short we had to verify that if it was the problem with the device itself. Well the process was lengthy and result could never be accurate. Hence it’s always preferable to use some tools which can give accurate results in less time.

What is Nokia Energy Profiler?

Nokia Energy profiler is a stand alone test and measurement application which lets you monitor the battery consumption on target device. This application will help you monitor the power consumption ,Check your internet connection speed., investigate cellular network’s coverage., watch the processor load during applications ,RAM memory usage and much more.


Nokia Energy Profiler is available for which mobile devices?

The Nokia Energy Profiler’s measurement features work only on S60 3rd Edition, Feature Pack 1 and later devices.

How to use Nokia Energy Profiler for Testing?

  • Run Nokia Energy Profiler(Keep this app in Background)
  • Perform testing on your Target application.
  • Once testing is completed, go back to the Nokia Energy Profiler application and stop the measurements
  • Save the results
  • Study the results or
  • Export results as CSV


What can I do with  Nokia Energy Profiler?
The Nokia Energy Profiler supports the following views:

  • Power View
  • Current.
  • Processor.
  • RAM Memory.
  • Network Speed.
  • WLAN.
  •  Signal Levels.
  • Energy.
  • Voltage.
  • 3G Timers.

From where  I can  get more details about Nokia Energy Profiler?

You can get further details about Nokia Energy Profiler Installation, Usage, Features here

From where I can download Nokia Energy Profiler?

You can download Nokia Energy Profiler from here

Posted in Mobile Application Testing, Mobile application Testing and Automation tools, Symbian Application Testing. 3 Comments »

Symbian Signed Tests Cases v 4.0.14

April 15, 2010 — anuragkhode

Symbian Signed Tests Cases v 4.0.14

This version of the test criteria is in effect from 5th January 2010.

Reference: Symbian Signed Test Criteria

TEST 1 — Installation
TEST STEPS
Before starting the test round, use a file manager to note the free user space available on the phone. You will need this information in test 8.
1 Install the application being tested.

The application must install without error.
2 During installation note the version number presented to the user.

The version number must match that specified during submission.
3 Verify that the application has successfully installed on the device by navigating to the area on the phone where new applications are installed.

The application should present one or more icon(s) on the phone.
Notes
For any submissions which do not appear obviously once installed, the submitter must include details in the submission statement of how successful installation can be verified.

If the content does not appear obviously on the device once installed, and specific instructions are lacking in the submission statement, then this test will be failed.
TEST 2 – Application start/stop behaviour
TEST STEPS
1 Start the application by selecting the icon or following the steps outlined in the submission statement

Navigate to the Task Manager and check that the application appears there.
2 Close the application from the Task Manager.

Exit the Task Manager, and re-launch the Task Manager.

The application must no longer appear in the Task Manager.
3 Start the application as in Step 1.

Go to the Task Manager to verify that the application is running.

The application must appear in the task manager.
4 Close the application from within the application UI and then return to the Task Manager.

The application must no longer be running and must no longer appear in the task manager.
5 Restart the application as in Step 1.

Navigate to the Task Manager.

The application must once again appear in the Task Manager.
Notes
An application which must run in the background does not need to appear in the Task Manager or present a UI so long as the developer justifies this behaviour during submission.

All applications must have some way of verifying that they are running on the device, though, and the developer should provide this information.
TEST 3 — Application credentials
TEST STEPS
1 With the application running, check the name of the application displayed on the phone.

The application must display the same name on the phone as stated during submission.
2 Note the functionality of the application as it runs on the device.

The basic functionality of the application must match that declared during submission.
Notes
Step 1 does not apply to applications which do not have a UI

VoIP applications must present a UI in order to pass this test.
TEST 4 — No disruption to voice calls
TEST STEPS
1 With the application installed and running use a second phone to call the test device.

The incoming call must be indicated to the user on the test device.
2 Answer the call on the test device.

You must be able to conduct a conversation with the other party without interference from the application being tested.
3 End the call in the normal way on the test device.

The voice call must be ended.
4 From the test device, make a call to a second phone. Answer the call from the other device.

The call must be indicated on both devices, and you must be able to conduct a conversation with the other party without interference from the application being tested.
5 End the voice call from the second device.

The call must be ended on both devices.
6 Place a test call to the emergency 112 number from the device.

*Please check in your territory for the approved way to make test calls to the emergency services.
Notes
If the application being tested has the MultimediaDD capability, and has audio functionality, then that functionality must be in use whilst this test is performed. Particularly, it should be checked that the audio from the application is faded down to allow the user to hear the telephone call.

VoIP applications will need this test running using both the handset held to the user’s ear and using a headset. The test should be run with a VoIP call in progress, and the incoming GSM call should be announced with call waiting tones.
TEST 5 — No disruption to text messages
TEST STEPS
1 With the application installed and running, send a text message to the test device.

The incoming text message must be notified to the user as per their alert settings.
2 Read the text message on the test device and choose to reply. Send the reply.

The reply must be received at the second device.
3 From the standby screen on the test device, navigate to the “new text message” option and create a new message. Send the message to the second device.

The message must be received at the second device.
TEST 6 — Auto-start behaviour
TEST STEPS
1 With the application running, find the settings for the application — either within the application itself or from the settings option on the device.

There must be an option which allows the user to enable/disable auto-start functionality.
2 Ensure that the setting for auto-start behaviour is disabled, and restart the device.

The application must not start on device boot.
3 Now change the setting so that auto-start behaviour is enabled for the application and restart the phone.

The application must start when the phone boots.
Notes
If the application does not have auto-start functionality, then this test does not need to be run.
TEST 7- No disruption to key device applications
TEST STEPS
1 Ensure that the contacts, messaging and calendar applications are populated with data and start the application as in Test 2.

After the application has been installed and used, the data entered into those applications must not be altered in any way without the user being aware.
2 With the application running, navigate to the messages application and create a new message.

Save that message to the drafts folder and then open and edit it.

Finally, delete the message from the drafts folder and delete a message from the inbox.

All of the above actions should be possible without interference from the installed application.
3 Navigate to the contacts application.

Create a contact, then edit that contact and then delete it.

The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change.
4 Navigate to the calendar application.

Create an appointment in the calendar. Edit the appointment and then delete it.

The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change.
5 Use the web browser on the device to go to a web page which is known to work on the network being used.

It must be possible to create a data connection and to access the web page selected.
Notes
If the application, as part of stated functionality, makes changes to user data then an exception can be claimed here. The functionality must be described in the documentation with the application and all data other than that mentioned in the user guide must remain untouched as described in the test case.

The data used in this test case is also needed for Test 8, so leave the data on the device when proceeding straight into Test 8.
TEST 8 — Un-install
TEST STEPS
1 Stop the application as described in Test 2 and uninstall the application using the system installer.

The application must be uninstalled without error.
2 Following the same steps as in Test 1, navigate to where you would expect to see the application icon.

The application icon must not longer be present on the device.

If you used another method to verify successful installation in Test 1 then use this method to ensure that the application has been uninstalled.
3 Check the contacts, messages and calendar applications to ensure that that the data present in Test 7 is still present in those applications.
4 Using the same file manager as at the start of Test 1 check that the amount of user space available on the device is either the same as that found in step 1 or that any difference between the space available before and after fulfils the following criteria.

a) Excluding user-generated and downloaded content, the application leaves no more than 100Kb of data on the phone after uninstall

b) Any data left on the device after install matches the explanation given during the submission process
Notes
You should start this test with the application data from Test 7 still in place on the device.
TEST 9 — Device adaptation
TEST STEPS
Note: The following test steps should be run on the list of devices corresponding to the UIDs specified in the .pkg file.

The lead device list can be found at http://tiny.symbian.org/devicetable
1 Install the application onto the device

The application should install on the device or present an error message to explain that it cannot install onto that device.
2 Launch the application.

The application should run on the device or present an error message to explain that it cannot run on that device.
3 Briefly examine the application whilst running.

UI elements should be functional and text should be readable in the main screen of the application.
4 If the device on which the application is currently being tested supports portrait and landscape screen modes, start the application and then switch between the screen modes.

The application should continue to be functional, and usable, in both screen orientations of the device, whether or not the application rotates in response to the screen mode change.
5 Close the application from the application UI

The application should stop running.
6 Uninstall the application from the phone.

The un-installation should happen without error and the application must be un-installed.
Notes
Applications which do not present a UI to the user in normal usage do not need to run this test.

On the primary device — on which all of the other test cases have been run – only step 4 of this test should be performed as all of the other steps of this test case are covered elsewhere.

Additional Tests for VoIP applications

Note that Test 3 and Test 4 both contain additional notes which apply to the testing of VoIP applications. Please read and apply these notes when running those tests on VoIP applications.

Test 10 — Additional emergency call testing for VoIP apps
TEST STEPS
Note: These test steps should be performed twice — once with a SIM card in the device and once without.
1 With the VoIP application running in the background, but with no VoIP call in progress, initiate an emergency call in the usual way.

The emergency call must be placed over the GSM/CDMA network successfully.
2 With the VoIP application running in the background with a VoIP call in progress, initiate an emergency call in the usual way.

The emergency call must be placed over the GSM/CDMA network successfully and the VoIP call should be terminated or placed on hold.
3 With the VoIP application in the background, and an emergency call active make a VoIP call to the device.

The incoming VoIP must be rejected, and the emergency call must not be interrupted.
Posted in Symbian Application Testing, Test Cases. 6 Comments »

How to Install Symbian Application in Device ?

December 2, 2009 — anuragkhode

There are three steps to install Symbian applications in device:

  • via USB Cable
  • via OTA
  • via Bluetooth

Steps to Install the application via USB Cable are :

  1. Connect Device to PC, with the help of Cable Cord .
  2. Select Device Memory or Memory Card folder of Device.
  3. Select and Copy .sis file of Application from PC.
  4. Paste them in Device Memory or Memory card folder.
  5. Disconnect the connected device and PC connection.
  6. Open Device Memory or Memory card folder in device.
  7. Click on the .sis file of the Application for installing the application in device.
  8. Allow all the permission which device ask at the time of installing app.
  9. Set the Device permission for application from Application Settings , Permission like :Network Connection , User’s Read Write data , Ask for Permissions.
  10. Open Application Manager Screen of Device .
  11. Click on Application Logo
  12. Application gets open , Run the application.

Steps to Install the Application through Bluetooth are :

  1. Switch on  Bluetooth in device (Settings->Connectivity->Bluetooth)
  2. Switch on laptop bluetooth.
  3. Select the .sis file of Application.
  4. Search the Device on which you want to send Application Files.
  5. Select the Device and send Application .sis file from PC with the help of Bluetooth.
  6. Application’s Files are received through message.
  7. Click on .sis file Message in Inbox of your device
  8. Application Installation process  gets started.
  9. Allow all the permission which device ask at the time of installing app.
  10. Set the Device permission for application from Application Settings , Permission like :Network Connection , User’s Read Write data , Ask for Permissions.
  11. Open Application Manager Screen of Device .
  12. Click on Application Logo.
  13. Application gets open , Run the application.

Steps to Install the Application through OTA (Over The Air) are :

  1. Open Device Web Browser(WAP).
  2. Enter the link for Application site for Download OR Enter the link of Getjar Site.
  3. After opning the site , Select Device from Device List.(In Most Cases there is no need to select device there is only need of GetJar site)
  4. After Selecting the Device, Click on Download Link
  5. Application .sis file gets downloaded on device and automatically start the installation process.
Posted in Mobile Application Testing, Symbian Application Testing. Tags: , , . 1 Comment »

Symbian Signed Test Criteria and Test cases

October 10, 2009 — anuragkhode

Please find here Symbian Signed Test Criteria document for Symbian Application Teters and developers.

Symbian Signed Test Criteria

Posted in Symbian Application Testing. Tags: , . 5 Comments »