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

There are few topics in quality assurance testing that cause as much confusion as smoke testing versus sanity testing. The two names would seem to describe very different practices— and they do! But people still get them confused, since the distinction is somewhat subtle.
Many organizations rely on HP Quality Center to design test plans and track test results. TestArchitect’s Quality Center integration makes working with QC as easy as pie. TestArchitect (TA) is a three-in-one tool for Test Management, Test Development, and Test Automation. Users can create and manage test assets, execute tests, track and analyze test results, ...
An automation framework is a way to organize your code in meaningful manner so that any person who is working with you can understand what each file contains. Automation frameworks differ based on how you organize your code – it can be organized based on your data, so that any person who wants to use ...
I’ve been teaching a lot lately, was in India for one week, and I’m off to Seattle in two weeks to teach on performance topics. I thoroughly enjoy teaching, it allows me to stay sharp with current trends, and provides a nice break from the “implementation focus” that I generally have day to day.
Introduction A characteristic of data warehouse (DW) development is the frequent release of high-quality data for user feedback and acceptance. At the end of each iteration of DW ETLs (Extract-Transform-Load), data tables are expected to be of sufficient quality for the next ETL phase. This objective requires a unique approach to quality assurance methods and ...
Test Automation is significant and growing-yet I have read many forum comments and blog posts about Test Automation not delivering as expected. It’s true that test automation can improve reliability while minimizing variability in the results, speed up the process, increase test coverage, and ultimately provide greater confidence in the quality of the software being ...
*You can check the answer key here
I got some comments on my post “Test Everything all the Time” — most notably people commenting that it’s impossible to test “everything”. I can’t agree more. The intention of the post was to make the point that we need to be able to test “everything we can” all the time. That is, you should ...
When it comes to performance testing, be smart about what and how you automate Listen closely to the background hum of any agile shop, and you’ll likely hear this ongoing chant: Automate! Automate! Automate! While automation can be incredibly valuable to the agile process, there are some key things to keep in mind when it ...
All too often, software development organizations look at automating software testing as a means of executing existing test cases faster. Very frequently there is no strategic or methodological underpinning to such an effort. The approach is one of running test cases faster is better, which will help to deliver software faster. Even in organizations that ...
The success of Automation is often correlated to its ROI. Here are 5 KPIs that we find universally applicable when it comes to quanitfying your Test Automation.
A short-list of selection criteria and popular automation tools. There are a lot of test automation tools available in the market, from heavy-duty enterprise level tools to quick and dirty playback-and-record tools for browser testing. For anyone just starting their research we’ve put together a short list of requirements and tools to consider.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe