|
One of the British IT companies being an acknowledged leader in the development and deployment of user interfaces for mobile phones, entrusted Bug Huntress with a task of testing its most prospective UI for mobile phone Themes, and the environment language generating graphic shell and simulating shell performance, in particular.
Bug Huntress objective
The task was to perform test cases on Symbian smartphones involving super-numerous routine user actions accompanied with obtained results analysis.
Bug Huntress challenge
|
For the detailed analysis of the task, Bug Huntress performed testing several times in manual mode. It appeared that 90 percent of tests did not require phone restart and/or connections. It was decided to apply in tandem Remote S60 and Rational Robot utilities. Remote S60 allows for user actions emulation such as button pressing and retrieval of the result on the PC screen as a phone screenshot, while Rational Robot performs button pressing for Remote S60 and performs the obtained results analysis in accordance with the models.
|
Initially the project has been estimated as requiring 200 man-hours and 200 PC-hours per cycle.
After the analysis made by Bug Huntress QA engineers, it was re-estimated as requiring 1,200 hours for implementation and only 5 man-hours to perform results analysis and 180 PC-hours.
Hence, the team reached 'payback' after the sixth iteration with a surplus of an innovative self-developed testing method.
|
Thus it was assumed the major part of the testing could be performed automatically during the night stand. Configuration testing was performed flawlessly and efficiently on account of starting the test cycle for a number of phones on a number of work stations simultaneously during night stand and performing the analysis of the results obtained during the next day, regardless of the quantity of mobile phones.
After the resource thorough analysis QArea decided to change the simulator significantly adding the analysis fields of states and events processing. It provided the possibility to create a graphic shell to use every language command at least once and display all the state changes.
First of all we checked the available shell on all the devices being simulated and compared the real results with the expected ones. Secondly, we developed test cases and respective types of testing for the simulator via automated testing tools; applied the test cases in testing the real devices and adapted the tests (scripts) by collating the screens. The chain is considered to be integrated provided there is no simulator testing, which is performed much faster then on devices.
Bug Huntress Solution
This solution represents an evolution testing, providing the possibility to locate an error clearly: nonoperability of the simulator will result in device disruption. Though the significant change took much effort and time, it helped saving time on further testing and it also provided the result tracing mode. This change made the process of a new functionality addition and an error change transparent. Another benefit is that we actually got a self-testing environment.
| 
QArea Newsletter
