Archive for September 2011
Testcomplete™ can be used to automate testing of Web & windows applications. Although TestComplete™ supports major standard controls, windows and objects in a wide variety of applications, there are some controls and windows that cannot be recognized by Test Complete directly. For example cells in few grid controls, buttons in some flash applications may not be accessible by TestComplete™. Handling TestComplete™ during such conditions makes automation little challenging.
It is possible to overcome these kinds of difficulties by using a low-level recording approach to test such applications. The main drawback of such an approach is that the script will require several changes even for a simple UI change in the application. So, creating and maintaining a stable script with this method is also not possible. Low-level Recording will be usually used in TestComplete™ for automating Testing in browsers other than IE and Firefox. Any application that needs to be tested in other browsers (such as Google Chrome or Opera) using TestComplete™ automation needs to approach low level recording technique.
In Test Automation, Data driven frame work is a most effective frame work which gives more test coverage, with less effort.
It becomes necessary for testing an application with different test data even in automation testing. While developing test automation for these types of application, Data-Driven frame work is best to use.
General Approach for creating data driven test:
- Record (or develop) your test scenario with a set of test data in your tool.
- Create data storage (Excel, csv or data base) and in which give multiple values for each test data.
- Replace the values in the recorded script with proper variables.
- Write script to access a set of test data from the storage, and assign it to those variables. While executing the test these values will be used.
United Testing Initiative (UTI), a collaborative organization focused on mobile application quality and consisting of representatives from AT & T, LG, Motorola, Nokia, Oracle, Orange, Samsung, Vodafone and Sony Ericsson have released the best practice guidelines for developing quality mobile applications. This can be found
I have culled out the user interface portion of the best practice guidelines and I have converted them into quality guidelines of mobile applications. The user interface quality guidelines of mobile applications should certainly have the following features:
- Keep the status bar hidden only when the application’s user interface is better without it
- Ensure that the back button always navigates through previously-seen screens
- Make sure navigation between application elements are easy and intuitive
- Ensure that the application uses relative layouts and device independent pixels, without making any assumptions about screen size, resolution, orientation or input.
Mobile apps are evolving rapidly making ubiquitous information, accessible anytime and anywhere across diverse devices. This has meant an increased need for ensuring the usability of the apps on the mobile and not just the functionality of the apps. Some of the common factors that influence usability of mobile software are:
Adopting PC approaches directly for mobile software
Most programmers who work on mobile software were trained to develop software for the desktop environment. There are many standardized practices in such a development environment and programmers with relatively low usability knowledge / experience can borrow standard interfaces and libraries and create usable programs.
In the case of mobile software things have not evolved as much. Moreover, for each mobile platform, there are new set of standards, technology used is different, look and operations are also different between platforms. This adds to the complexity of mobile software while adopting desktop approaches to developing them.
Mobile web application usage is increasing by the day as the mobile penetration is multiple times larger compared to PC penetration. All businesses and organizations that are looking at leveraging the mobile medium should ensure high performance of their mobile web applications lest their end-users will move on to other providers apps.
The predominant issue with most mobile web apps is related to the speed at which the application loads. This would affect the bottom line and it becomes necessary to monitor and optimize the performance of mobile application and the supporting infrastructure for better user experience. As it is, the mobile application spectrum has a number of challenges such as the uncontrolled and unpredictable nature of web apps, limited visibility on the end-user experience, and difficulty in identifying and resolving problems.
The answer seems obvious, or does it? After all, the application on a mobile device has the same functionality as the application on a standard desktop computer or laptop. Well, the difference is that mobile apps have to be tested for their non-functional aspects (such as usability) on mobile devices and not just primarily focused on functional testing.
There are a number of challenges that are a direct result of the unique features of mobile devices and wireless networks:
Mobile context – interaction between the users, applications and the surrounding environment that may distract user’s attention
- Connectivity – slow and unreliable wireless network connection with low bandwidth is a common hindrance for mobile applications
- Screen size – physical constraints of mobile devices, especially small screen sizes