Mobile Internet- Mobile test platform
As mobile Internet applications gain huge popularity, mobile platform operators and application providers are anxious to test applications’ performance and functionality on multiple handsets and mobile operation systems. However there are over a hundred of combinations of cellphone brands and models, such as common smart phone operation systems Android, Mobile Windows, Symbian, Linux and OMS. So, how do we minimize the test cellphone purchase cost while cover the mainstream cellphone models and OSes to the largest extent, and improve reliability before release?
Sigma test experts realized the same problem. We developed remote test platform SMC, which is designed to test mobile applications’ compatibility with popular handset brands/models and ensure nice user experience. The remotely accessible cellphone list covers an overwhelmingly majority of models at present, saving a great deal of test machine purchase expenses for customers. The application developer can conduct real remote operations (different from simulation acts) through WebUI, and verify functionality/performance indices of the mobile program. In addition, the platform supports a very cost-effective feature of time-sharing, i.e. customers can reserve cellphone use hours to make the best use of platform resources.
The platform, based on JavaEE web technology, conducts secured HTTP data transmission by HTTPS, and it checks user’s log-in validity prior to execution of each action. The platform with MVC layer technology reduces inter-layer coherence with more system flexibility and scalability. The test benefits from Sigma’s real cellphone pool of nearly 200 different models, which are accessible through a direct connection with server by USB hub, and covers largest percentage of handset modules.
With JavaEE Web technology, users with installed JRE are able to access the platform in IE/Firefox browsers.
Specify brand/module of the cellphone and reserve use hours after login.
A webpage with the specified cellphone brand/model interface and keypad is returned after the user’s access right is authenticated, for user to conduct real-time remote operation. Take Nokia E71 for instance, the screen is captured from a real cellphone and sent back to WebUI, which beeps to confirm the reception of operation command as a user presses on a function key. The WebUI will then refresh to display the command-related features:
- The user can select a test software kit and upload it to cellphone, and then install it for a remote control by manual approaches.
- Remote control cellphone for manual testing
- Download the test logs from cellphone to local PC for debugging.
- Instruction of script integration into different physical environment
- Select a different platform and cellphone, repeat the test
We have two sets of QA processes for the scripts we developed. One is the general product development quality control:
- System administrator is responsible for proper operation of the entire system’s hardware/software parts.
- Testers authorized by the platform operator are responsible for creation/adding of group/individual users, as well as the modification/binding of cellphone use hours.
- Common users - individual testers pay charges respectively.
The system conducts a real-time health check on all cellphones under test, and notifies the administrator to debug as such defaults occur and trigger alarm: no reaction as the WebUI key is pressed, backend cellphone system freezing/crush/blue screen, power down and other hardware defaults leading to cellphone reactionlessness.
Individual users can pay for the reserved use hours online by cellphone banking, Alipay and other 3rd party operators; group users can sign payment agreement with the SMC operator. They can also buy a certain period of time, such as a 100-hour prepaid card from operator, and consume the hours as they need. Alternatively, they can buy exclusive use hours of a certain cellphone model(s), and pay by repaid recharge card or sign agreement with operator.