TestArchitect Corner: Leverage Mobile Testing with TestArchitect

layer-98

Mobile usage today is not just a trend but it is an essential shift in how people communicate with each other, interact with the world, and do business. According to a ComScore, in 2014 the number of mobile users surpassed the number of computer users and is showing strong growth over time, towards some point in the near future where virtually each person on Earth will own at least one mobile device.

number-of-global-users

Therefore, it is no longer a case of asking whether building mobile apps or mobile compatible websites is essential for any business. It is. “Mobile first” has become a motto for many companies nowadays to keep up with the race of mobile age, in order to retain customer loyalty.

Users quickly uninstall a mobile app if they encounter an application bug, slow loading speed or incompatible issues with their devices, so making sure the application works seamlessly on any device is vital. On the other hand, developing and testing on mobile devices are quickly getting overwhelming because of the variety of operating systems and their versions, of device makers and models, and of screen sizes and resolutions. And that doesn’t even cover the various input methods, carriers, data transference speed, GPS, accelerometers, and application kinds: native, web or hybrid apps.

Add to this the extensive infrastructure of backend systems to support the mobile applications and their usage. Clearly, testing plays an important role in ensuring that requirements are met by ensuring apps run well and consistently on a set of different target devices. However, creating and managing large amount of test cases which cover all combinations of mentioned variances in a short of time is not an easy job.

The TestArchitect automation tool relieves these concerns in an elegant way by applying Action Based Testing methodology into test design to quickly create tests. No programming knowledge is required and maintenance effort is kept at a minimum. For the test execution, TestArchitect allows user control via cable and/or Wi-Fi from one host machine up to 20 devices, that can also include simulators. A user can use the screenshot capturing feature to record the run on each device.

When the execution completes, the test results of each device will be collected by the host machine. From the test results, QA staff can see if the application under test has issues on specific devices and work with the development team to fix the issues before releasing the app to the market.

In addition to the mobile support TestArchitect supports a wide range of platforms like desktop, web, and non-UI, for example database access and REST service calls. This allows you to flexibly combine device level testing with related testing on the backend systems.

 aaa

Van Pham, Product Support Manager

Van Pham has more than 10 years of experience in software automation testing on various platforms and Customer/Product Support. A key member of the organization, Van mentors, manages, and motivates LogiGear’s Support teams to provide an exceptional Customer Support Experience. Van has her B.S. in Software Engineering from National University, and an M.S. in Engineering Management.

Van Pham
Van Pham has more than 10 years of experience in software automation testing on various platforms and Customer/Product Support. A key member of the organization, Van mentors, manages, and motivates LogiGear’s Support teams to provide an exceptional Customer Support Experience. Van has her B.S. in Software Engineering from National University, and an M.S. in Engineering Management.

The Related Post

September Issue 2018: The Secrets to Better Test Automation  
5 roadblocks in vehicular autonomy that complicate Software Testing Experts in the field have previously referred to air travel as somewhat of a gold standard for autonomous vehicle safety, but after Boeing’s two tragedies, that analogy can no longer be used when talking about self-driving cars. This was after Boeing’s 737 MAX Jets have found ...
How lagging automotive design principles adversely affect final products. Cars are integrating more and more software with every model year. The ginormous screen introduced by Tesla in their flagship Model S a few years ago was seemingly unrivaled at the time. Nowadays, screens of this size are not only commonplace in vehicles such as the ...
Based in Alberta, Canada, Jonathan Kohl takes time out of his busy schedule to discuss his views on software testing and automation.
Picture a series of sprints: There are a variety of features being developed, with an eye towards having automated tests related to those features. Work starts to move along and Test Automation work likewise goes along with it. However, at some point, there invariably is that moment, usually in the middle of the project, where ...
It can be complicated to automate model-based testing. Here’s how to employ action words to get the job done.
Mobile testers need to take a different approach when it comes to Test Automation.
Automated Testing is a huge part of DevOps, but without human-performed quality assurance testing, you’re increasing the risk of  lower-quality software making it into production.  Automated Testing is an essential DevOps practice to increase organizations’ release cadence and code quality. But there are definitely limits to only using Automated Testing. Without human quality assurance (QA) ...
LogiGear Magazine – October 2010
Test automation provides great benefits to the software testing process and improves the quality of the results. It improves reliability while minimizing variability in the results, speeds up the process, increases test coverage, and ultimately can provide greater confidence in the quality of the software being tested. However, automation is not a silver bullet. It ...
Introduction As a consultant and trainer, I am often asked by my clients and students how to deal with automated acceptance tests. One common question is whether automated acceptance tests should use the graphical user interface (GUI) provided by the application.
Test execution and utility tools that can make your job easier My first exposure to the necessity for testers to have an array of tools was from the groundbreaking article “Scripts on my Toolbelt” by Danny Faught. Danny laid out the ideal approach to any testing job, and it got me thinking “How can I ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe