Manage Learn to apply best practices and optimize your operations.

How to track configuration changes in mobile app testing

Amy Reichert reviews tips on how we should track configuration changes in mobile app testing.

Configuration changes are updated constantly in mobile application development as development companies try to...

keep up with demand. Mobile app testing, on the other hand, is already complicated by the number of paths needed to ensure a quality product. The process is burdened by testing requirements around screen size, platforms, connectivity and configuration.

With an already full plate, how does a mobile app testing team add in testing configuration changes in a release? Typically, configuration settings are not the highest priority changes, so testing them falls behind other feature testing commitments. You can try a couple of options to see what works for the mobile app testing team's schedule.

The first is random selection. For example, if there are 20 configuration changes pick the top 10 that are most important to clients, or that occur in the most-used features. Or list each by priority or importance and by the popularity of the associated feature and test your way down the list.

Testers also can divide the list between releases. Granted, not all features will be tested in the initial release, but a group can be tested each release until testing is completed. Create rotating test suites and mix them into your regression testing executions. Once each has been thoroughly tested, go back through and mix them at random or by feature and add them to the regression test along with their matching feature.

Another logical option is to test them with the feature they control. If the testing numbers are too high rotate the feature and create small subsets of test suites that cover a piece of each feature. Switch out testing suites each regression cycle. Each testing suite contains a portion of every feature so in this way, full testing occurs over a series of regression testing events but all features are covered to some extent.

Next Steps

Accelerating mobile app testing

Mobile testing criteria

This was last published in July 2015

Dig Deeper on Exploratory Software Testing

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

3 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

How do you track configuration changes in mobile app testing?
Cancel
Really a great article @Amy Reichert.
Cancel
Thank you! I sincerely appreciate your readership!
Cancel

-ADS BY GOOGLE

SearchMicroservices

TheServerSide.com

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

DevOpsAgenda

Close