The mobile testing process is not suited to a one-size-fits-all approach. There are different goals that require different types and levels of testing at different stages in the process. These needs dictate whether to test manually or to automate testing. Automated testing may not be right in every mobile testing scenario, but in most cases it can save significant amounts of time and money and improve the effectiveness of QA testing process.
It is a challenge for us to test Android, iOS, Blackberry, Windows, etc. all from the same platform. Smartphone and Tablet app testing is often very repetitive and time consuming. We noticed that an advanced support for HTML5 web-based app development including object level scripting can let you to run one script across all device platforms.
Using a multi-tiered scripting technology helps to create keyword driven and requirements driven test scripts. It offers to create high level device-agnostic test scripts that can be used across multiple devices – making test script maintenance and porting easy.
Our tester's plug-and-play local devices into their desktop computers for manual and automated testing. During the testing, they have a control over the hardware functions of the mobile device like power detection, backlight detection, power on/off, battery connect/disconnect, SIM card etc. A visual, WYSIWYG drag and drop interface is present to test the application.
Our testers run ad hoc or schedule test cases for specific days or hours. They are able to integrate UAT, functional, regression tests and perform an end to end integration testing. The test cycles are created to run multiple test cases across multiple devices. A dashboard is present to enable users to view devices in real-time as test cases are executed.
It is noticed that our automation of mobile application testing reduces the mobile testing man hours by 75% and increases the execution rate of the test cases by 3 times.
We used Microsoft Visual Studio 2010 with the load test pack add in, that was available as part of the existing MSDN subscriber licenses of our customer, thus saving substantial costs for our customer during performance testing of the application. All the user scenarios and test data were designed by in-house Subject Matter Experts along with the test engineers. We also recommended the use of a specialized third party vendor for security and penetration testing to reduce costs by reusing existing licenses that customer had.
By following industry best practices and capturing all testable requirements and conducting Independent Verification and Validation of the software, our quality assurance team made sure that the final product was a quality product matching all of our client's expectations.
No comments:
Post a Comment