Mobile App Performance Testing

Do I Need Mobile App Performance Testing?

Mobile app performance testing is the process of testing and reporting the time it takes your application to process a request or take an action – especially when large groups of users perform the same or similar action simultaneously.

Performance testing answers the question, “When and where does the performance and speed of my application degrade the user’s experience?” It also answers the question, “How many users can I have before my application crashes?”

Performing “At Scale”

“At Scale” is the current lingo for “many, many, many users and transactions”. Performing “At Scale” is a big concern when building software and especially mobile apps. Mobile app performance testing helps you understand the scale your mobile app can withstand before degrading or crashing. Most software development teams invest significant time and money engineering their mobile apps to perform at scale from the very beginning. This is generally a wise investment but only if you are willing to apply mobile app performance testing throughout the software development process. Otherwise, the software development team will not have the feedback they need during the software development process to measure and correct the scaling assumptions they had to make while building your software.

Performing “Good Enough”

If “At Scale” is not a critical business and technology driver for your mobile app, you still might need to be concerned about performance and mobile app performance testing.

Here’s why:

  • All mobile applications have performance limits
  • When mobile application performance degrades and slows down, users abandon mobile apps.

You’ve invested serious time and money building your mobile application. Don’t you want to know how many people you can satisfy with your mobile application before they become dissatisfied?

There’s a big difference between engineering and performance “At Scale” and “Good Enough”.

Engineering and mobile app performance testing “At Scale” is an ongoing endeavor to insure that your mobile application will always be available to as many users as possible. This is an expensive process but worth it when your goal is performing “At Scale”.

Mobile app performance testing  for “Good Enough” is an end-of-cycle process that determines “How many users can I handle before I need to turn on more servers?” This is a much simpler and less expensive process that gives you a finite number and an alert for when you need to add more servers in your AWS or Rackspace cloud.

If you aren’t required to engineer, build and deliver “At Scale”, then “Good Enough” may work best for you. A short engagement to determine “Your Number” will help you recognize and avoid a disaster where your mobile application performance degrades and you lose customers. You’ll use “Your Number” to alert you to add more server capacity before your known performance threshold and prior to any perceived slow downs by your customers.

Look Before You Leap

You want good testing results, of course. Or put another way, you want good testing value. That’s why it’s crucial to define the mobile testing strategy first, which includes performance testing, before thinking about a test plan.

Defining The Mobile App Performance Testing That’s Right For You

Want to discuss your situation? Call me 888-254-9709. Or, click the green button on this page to request a call back.

Share This:
Mobile Testing Strategy

The Difference Between a Mobile Testing Strategy and a Mobile Testing Plan

There is a big difference between a mobile testing strategy and a mobile testing plan. If you know the difference, your mobile software testing will be much easier and more valuable.

There are a number of ways of defining a strategy. One of the definitions that we’ve found useful is:

“Identify assets that have advantages that you can put into coordinated action to achieve your goal

Or, said another way, list and organize everything you think you’ll need to achieve your mobile testing goal and why you think you need it.

Your goal should be clear enough that you can quickly see what is, and is not, relevant to achieving your goal.

For example, if your mobile testing goal is to release your game every week with new features and fixes, your strategy might be different from a goal to release a zero defect trading app. Already, you can start to see that you might need different Assets for each of those goals.

Your Goal Will Dictate Strategy

One of the first challenges in building your mobile testing strategy will be to clarify and tighten your mobile testing goal. Your goal should clearly show what is and is not important to include in your mobile testing strategy.

The biggest and best tool you can use to uncover gaps or weaknesses in your mobile testing goal will be relentless Critical Thinking Questions.

“Why is this important and what, exactly does it mean?” is one of the most powerful questions you can ask about your mobile testing goal.

For example, which devices should you test against? The answer depends on which devices your current customers or prospects are most likely to be using. You know that mobile apps behave differently on different devices and operating systems, right? You won’t be able to afford to test against every device out there – you’re going to have to make some assumptions and then test their validity.

The more you can refine your mobile testing goal by clearly understanding what is directly relevant (need to have) and which things are “nice to have”, the more effective your mobile testing strategy will be.

A List of Things to Decide for Your Mobile Testing Strategy

Since you’ve made it this far, you probably realize that your questions are far more important than your answers!

Here is a list of questions that you can use to help you narrow your focus and build an effective mobile testing strategy:

  1. Which devices are important to my target audience?
  2. Do I have to have the real device or can I use an emulator?
  3. Can I use a tool for testing and do I have the experience to use it properly? Which tool will meet my needs and how can I tell that?
  4. What network connectivity is required for my app? Wifi? Cellular Data?
  5. Which parts should be automated testing and which should be manual testing? What’s the proper balance and how will I know?
  6. Will I need performance testing for my mobile app? Why would I need performance testing and which parts of my mobile app are subject to
  7. network congestion?
  8. What are the security requirements for my mobile app and how do they need to be tested? What is the probability and impact of a security
  9. breach of my mobile application?
  10. What sort of UX testing do I need and who is best qualified to give UX feedback on my mobile app?

Whew! Those are not easy questions!

And yet, you do need to know those answers if you want to avoid a “just get it tested” type of strategy.

So, is there an easy way to get started and build a great mobile testing strategy?

Start with a Free Scoping Session with Me

I know, that sounds generous and it is.

And, we can do that for and with you in one of our standard 60-90 minute Scoping Sessions.

Most of our clients and prospects don’t have a quality goal prior to meeting with us. Only one or two have ever had a quality strategy when they first came to us.

So, we’ve become very adept at helping our clients and prospects define their quality goal and build an effective testing strategy.

We do this by gently asking you a lot of questions. Sure, we want to know the details about your mobile app and how you want it tested. We can and will do that for you.

And, we want to make sure we provide you with everything you need to achieve your goal. So, the first thing we do for you is clearly define your goal and then propose a couple of different strategies for you to consider. We’ll always recommend at least one of the strategies but we want you to know that there are different ways to achieve your goals and that you have the last word on how we work for you to achieve your goal.

If you’re curious about how a mobile testing strategy can improve your mobile app testing, achieve your goals and build your business stronger, please reach out and let’s talk about how we might help you. Send the form on this page to schedule a call, or give me a shout now at 888.254.9709 .

 

Share This:
Automated Mobile App Testing

When Is Automated Mobile App Testing The Right Solution?

Automated mobile app testing seems like a silver bullet to the problem of testing your mobile app quickly and inexpensively. After all, computers can run tests faster than humans and don’t need breaks or time off. And, seldom does a day go by that you don’t hear a story about a business using process automation to improve their speed to market and lower their human costs. Seems like a good idea, right?

Well, one of my business mentors taught me that all my biggest problems started as a good idea that I failed to explore in detail before starting on it.

Here are three things you should consider before starting your automated mobile app testing.

Issues To Consider About Automated Mobile App Testing

  1. Automated testing is more expensive than manual testing but the cycles times should be shorter.
  2. Automated tests have to be constantly maintained and updated just like your mobile application.
  3. Automated tests with false positives are worse than no testing at all.

Speed Versus The Rise of False Positives

One of the primary benefits of automated mobile app testing is the speed at which the testing can be completed. Faster testing cycles means faster mobile app releases which allows you to seize more opportunities. The higher up-front costs for automated mobile app testing should be offset by faster release cycles. But, is your mobile app development team really ready to go faster? How much faster and what might happen if it’s too fast?

A distinct drawback to automated mobile app testing is the constant need to update your automated test scripts to match the new and changed functionality in your mobile app. An automated mobile app testing system can only test when it has been told to test and nothing more. If you change your mobile app, then you need to change your automated mobile app tests – every time.

And a common failure in automated mobile app testing is the rise of false positives over time. A false positive is when your automated mobile app testing systems reports a defect but it isn’t really a defect. Your mobile app is correct and your automated mobile app testing system is wrong. It is probably out of date and trying to test the last version of your mobile app and not the current version where functionality has changed. This results in false positives that have to be categorized, prioritized, verified and then resolved. If your automated mobile app testing system is reporting false positives, you will waste and enormous amount of time and money chasing them down.

How To Do Mobile App Performance Testing Right

The ideal situation for automating your mobile app testing is when you have a relatively stable mobile application and you and your development team are committed to increasing your process automation. The best reason to automate your mobile app testing is to improve your software release speeds and reduce human error due to repetition in your testing cycle.

Automating the testing of a relatively stable mobile app produces far better results than trying to automate a young or new mobile app. There is a minimum investment required to build a test automation harness that will then be filled with automated tests. A young mobile app presents a very difficult target to automate due to the highly dynamic and changeable nature of the app. A young mobile app, by definition, is subject to numerous changes as the team works to try a variety of different approaches to please their customers. Automated testing for a stable app is easier to build, less costly to maintain and more accurate in it’s results.

The Impact You Can Expect

Make no mistake, automated mobile app testing will have an impact on your development process. You’re probably using a small collection of dev automation tools to help you manage your codebase and produce a releasable version. Adding automated mobile app testing into your automation stack will require someone on your team to manage and integrate it into your overall system. You and your team will need to be ready for this.

Lastly, automated mobile app testing is more expensive than manual testing but it is faster and more accurate. Since that’s the case, the only really compelling reason (and it is compelling in a *lot* of cases) is to increase the speed and reduce the time needed to release new features into your mobile app. If getting “faster” isn’t a distinct market advantage, it may make more sense to look at other alternatives to automated mobile app testing.

Confused Yet?

Automated testing, especially for mobile applications, is an important decision and worth evaluating (and re-evaluating) on a regular basis. It can be an expensive investment and you’ll want to make sure you’re getting the biggest bang for your buck.

The best place to start is a conversation about what might be possible for you, the goal you’re working to achieve, the strategies available to you to achieve your goal, and the costs and benefits of each strategy.

I help managers straighten out their mobile testing strategies every day. Sometime I even get paid for it.  If you’d like to talk about your options, I’d  like to listen. Call me at 888-254-9709, or click the green button on this page to request a call back.

Share This:
Mobile Application Testing Strategy

Why You Need a Mobile Application Testing Strategy

App testing looks easy but you might want to think again – and I’ll help you think through a mobile application testing strategy.

Simple, but not Easy

You can very easily skip or ignore some very important risks just because you didn’t even know to think about them! Mobile application development moves very fast, is usually highly agile and covers much more than just the mobile app itself. Most mobile application testing projects spend too much time on functional testing and not enough time finding and reducing real technology and business risks.

Starting to test your mobile app without a Testing Strategy can result in a “well tested” mobile app that frustrates customers, scares off prospects and lights up the support phone and chat lines.

All because you didn’t know what you didn’t know!

And that’s probably not what you wanted or expected.

A simple mobile testing strategy will help you find the important risks, plan your testing work to focus on the important areas and reduce the time and money you spend launching your mobile application.

What You Don’t Know CAN Hurt Your Project!

There are six  important subject areas in that you need to consider in your strategy for testing your mobile application.

  1. Devices – What is your list of most important devices? What devices are you willing to exclude or not test? Do you have access to those important devices?
  2. Networks – What networks will your mobile application use? Are they cell networks or wifi networks? What happens when your mobile app switches networks?
  3. Servers – How much of your mobile application functionality depends on accurate information from a server application? Most mobile apps rely heavily on back-end servers to do the heavy lifting work while the mobile app itself mostly accepts inputs and display outputs. What happens in between your server and mobile app?
  4. Performance – What are your minimum performance times for functions in your mobile application? What are the upper limits of your server? How many simultaneous users do you expect? What performance tools are provided by your server hosting company?
  5. Security – How secure does your mobile application need to be to protect your user’s information privacy? Is 2FA important to your users? How secure does your server need to be?
  6. UX (User Experience) – Will your users find your mobile application enjoyable and easy to use or frustrating and confusing to use? What UX data will you collect to help you understand this? If a user does leave, how will you recover them?

If you know the answers to these questions, you’ll be able to clarify your goals and build a mobile testing strategy to achieve them for your unique mobile application.

Curious yet about TESTCo’s mobile app testing services? Here’s more information on our capabilities.

No Mobile Application Testing Strategy? Here Comes the Pain.

If you don’t answer those questions, you can expect to see (and feel) some of these pains:

  1. Your mobile works fine on the most recent iPhone but fails with previous versions of iOS and some Android devices. And, only a small portion of your audience has the most recent iPhone.
  2. Your mobile application works great on Wifi but fails with errors on a cellular network if a user is talking on the phone and using your app.
  3. Your mobile application fails and crashes when the server is slow returning complex query results.
  4. Your mobile application works fine until there are over 900 simultaneous users – and then it displays the wrong query results.
  5. Your mobile application is easily penetrated and accounts are hijacked.
  6. Your mobile application UI works great for the engineers who built it but ordinary users struggle to understand how to use it.

Build Your Own Simple Strategy – or Let Us Help You!

The best solution is to build a simple mobile application testing strategy unique to your project. It’s easy if you follow this guide I recently published.  At TESTCo, we build and evaluate several test strategies for every software and mobile application testing project. If you don’t want to build your’s, we can build it for you!

Schedule a call with me using the green button on this page, or call me at 888-254-9709

Share This:
Mobile Application Regression Testing

Why Regression Testing Must Be Included in Mobile Application Testing

Are your mobile apps prone to breaking after implementing a new feature or update? If so I encourage you to make mobile application regression testing a regular part of your test plan?

You see, after an update or new feature has been added there’s a really good chance that you have some new defects in your older, previously working code. Why might that happen? There are several reasons that your previously “good” mobile application now has new defects after your last update.

Why Defects Appear in “Good” Mobile Applications

  1. Changes in the mobile operating system – it is not uncommon for changes and improvements in a mobile operating system to have a negative impact on your mobile application. This isn’t intentional nor does it happen every time. Testing on a variety of mobile operating systems and devices can help you find these regression defects quickly. Knowing which operating systems and devices to test is where professional mobile application regression testing can help you save time and money.
  2. Changes in code module dependencies – most mobile applications are built by assembling a set of basic software components and then customizing how they interact with each other and your customer. These basic software components are almost always being changed and improved. When those new changes and improvements are included in your new mobile application version, errors are likely to occur. Writing test plans to specifically test mobile software component interaction will help you find these types of regression defects. Professional software test engineers know and use effective test strategies and plans to help you identify and test these “risky” areas.
  3. Human error in development or testing – humans make mistakes – sometimes knowingly and sometimes without knowing. Most regression defects caused by human error are not intentional – in fact, just the opposite! Human errors typically occur when an improvement in one area of the code has a negative impact on some other area of the code that wasn’t foreseen by your software developer. For example, improving the user experience for logging in may have an unexpected impact on how a password reset request works that cause it to fail. QA managers, as an integral part of a mobile application regression testing team, can help you better understand how your requirements/user stories can show you clues to find these types of regression defects.

Smart Mobile Application Regression Testing Begins with a Smart Test Plan

Regression testing doesn’t fit easily into an Agile software development process. And yet, going without regression testing for your mobile application can lead to loss of prospects, customers, and revenue. Working with the right outsourced mobile app testing company certainly goes a long ways to removing the risk associated with rolling out mobile app enhancements.

Go ahead, call me. 888-254-9709. Even if you just want to pick my brain, I want to hear from you. Or, if you prefer, click the blue button on this page to schedule a call back.

 

Share This:
Mobile Application Testing Company Selection

How to Select a Mobile Application Testing Company

Mobile application testing is similar to software testing.

But, it’s also a little different in a couple of  key areas.

“Walled Garden” Software Distribution Challenges

Releasing your mobile software requires “approval” from a third party prior to listing on Apple Store or Google Play. How will this requirement impact your release dates and software testing schedule? What do you need to know to avoid Apple or Google declining your mobile app?

Inputs & Navigation Vs Display & Calculation

The intense focus on Inputs and Navigation in mobile apps requires different software testing strategies to avoid wasted time and effort. How will you know you’ve tested the most vulnerable areas in your mobile app?

Devices, Browsers, Networks and Emulators

So many and growing every day! Your mobile software will operate slightly differently on various device, browser and network combinations. Which combinations are required and which are optional? Which combinations need testing on a real device or network and which can be tested on an emulator? Making the wrong choice can cost you prospects and customers!

Test Engineers & QA Managers Vs Testers

Almost anyone that has used a mobile device “can” test your mobile app. But should they? Test Engineers coupled with a QA Manager can give you full QA coverage and Risk analysis. Testers can usually do what you tell them to.

Not every software testing company will know these key areas well enough to meet all your needs as a mobile application testing company.

Where to start?

There are many mobile application testing company choices available to you. What should you consider and where should you start to make your selection?

  1. Clearly define your quality goal and your budget for time and dollars. This will help whoever you select to build an accurate proposal/estimate. There will always be more QA work that is needed but business decisions drive mobile software projects. Time and money are key constraints that limit what can be done.
  2. Mobile application testing experience is critical. Mobile application testing is different than testing regular software and requires different tools, patterns and methods. Likewise, mobile application developers are seldom a good choice for testing your mobile application. Software test engineers are your best choice.
  3. The size and recency of the device and emulator library will dictate how successful a mobile application testing company can be for you. The wide variety of mobile devices and operating systems dictates that you make two wise choices.
    • Which devices and operating systems are most important to you and your customers?
    • Which devices does your mobile application testing company actually have? When a particular device/operating system is not available, an emulator must be used instead. Emulators are useful for some testing but almost always fail to provide the complete testing coverage that most modern mobile applications require

The Cost of a Bad Choice

You must already be convinced that testing your mobile application is important and needed – as evidenced by your visiting this page.

Congrats! Some of your competitors either don’t bother to test their mobile application or do it poorly.

Don’t believe me? Just download one of them and see how long it takes before you can crash it. Not long, right?

Here are the big costs you need to avoid when selecting your mobile application testing company.

  1. Price Vs Cost – in software testing, you really do get what you pay for. Low rates/prices are the teaser and longer projects, poor defects, missed coverage and blown out deadlines are the true cost. Compare their calculated project cost instead of the hourly rates. Then,  get a money-back guarantee to make double sure. Even better, get a fixed price for your project.
  2. Talent Vs Availability – not everyone is a talented Test Engineer. In fact, most “testers” aren’t engineers at all. If your problem can be solved by “just get it tested” then almost anyone will do – and there are plenty of those folks out there. If your goal is “on time with zero defects” then you’ll need talent – Test Engineer talent and QA Manager Talent. And yes, the price for a Test Engineer is higher but see #1 above.

The Keys to Successful Mobile Application Testing

The three key areas where mobile app testing differs from software testing are:

  1. Faster and Simpler – mobile application projects are usually faster to start and complete since they are smaller and more focused. Applications on mobile devices are also usually simpler in functionality than software applications due to limited screen real estate and uncertain connectivity.
  2. Experience and Completion – mobile apps typically focus more heavily on the user experience than most software applications. Also, clear evidence that the transactions made in your mobile application have been completed are more important due to the tendency of mobile applications to lose network connectivity.
  3. All Those Different Devices – software applications and (most) web applications run in a web browser on a desktop operating system. There are a finite number of operating systems and web browsers that need to be tested against a software or web browser application. There is an almost infinite number of mobile operating systems/browser combinations – definitely more than you could possibly test.

With these three big differences in mind, can you see how selecting the right mobile application testing company might be important in the success of your mobile application project?

Questions for Your Next Mobile Application Testing Company

Here are some great questions to ask when you’re shopping around for a company to test your mobile application.

  1. With our very fast sprints, how will you design your testing strategy to help us increase our speed?
  2. Since we have very simple functionality, how much and what type of testing do you propose to make sure we achieve our goal of Zero Defects?
  3. What strategy do you propose to test the usability of our mobile application?
  4. How will you test and validate transaction completion and notification? How will you test graceful failures?
  5. What is your strategy to help us figure out which devices to test on and which devices that an emulator should be OK?
  6. Is hard device testing necessary or will a tool or emulator be sufficient? Which tools/emulators do you recommend and why?
  7. Where does test automation fit into your strategy and why do you recommend it?

Mobile application testing is similar to but different enough from traditional software testing that a slightly different approach to selecting the best mobile application testing company can mean the difference between your success and failure.

Want to talk with someone at TESTCo about how we’d test your mobile app? Most clients, at first, aren’t even sure how much testing will be necessary. We will give very practical advice in the first call. Call and talk to me personally. 888.254.9709 Or, click the green button on this page to schedule a call back.

Share This:
Mobile Application Testing Services Choices

How Much Testing Does Your Mobile Application Need?

Mobile applications are different than web or installed applications and deserve some careful thought to make the best choices about what and how much mobile application testing services are really needed.

There is a long list to consider and surprisingly, you probably don’t need all of those mobile app testing services to achieve your goal.

Mobile application testing services can include:

  • Mobile application functional testing
  • Mobile application regression testing
  • Mobile application cross device testing
  • Mobile application test automation
  • Mobile application security and penetration testing
  • Mobile application performance testing
  • Mobile application usability testing

Goals for Mobile Application Testing Services

Here are some questions you can consider to help you determine if one of the types of mobile application testing services I listed will help you meet your needs and achieve your goal.

First, what is your goal for your mobile application?

  • How many downloads or users do you want to use it?
  • What value will your users receive from using your mobile application?
  • How will you know they have received that value?

Now that you have a basic goal for your mobile application, see if the following questions help you chose the best and most appropriate mobile application testing services.

Mobile Application Functional Testing

Does you mobile application contain complex or simple functionality?

Simple functionality with only a few inputs/outputs/screens usually doesn’t need anything other than some basic validation that the inputs/outputs and screens work and flow properly. There are few inputs/outputs/screens so the number of combinations to test will be limited and can be accomplished relatively quickly.

Complex functionality where you have more than just a few inputs, outputs and screens probably needs (and deserves) a more robust testing strategy and plan. In general, you can’t test everything (it takes too long and costs too much) so selecting a smart test strategy will be very important to make sure that all of the “Important Stuff” is tested thoroughly and frequently. Almost any qualified Test Engineer or QA Manager will have a small library of Test Strategies and can help you select the one or two that most closely match your needs and goals.

Mobile Application Regression Testing

Regression Testing helps you make sure that you didn’t break anything that was previously working well. The main goal of regression testing is to insure that you don’t disappoint or anger your mobile application users instead of delighting them with new features and functions.

Mobile applications tend to be updated frequently. One of the benefits of a mobile application is that they tend to be smaller and simpler than other types of applications and can be updated very quickly and easily. This is a tremendous benefit because it allows you to quickly add or change features based on real-time user feedback.

But, being very quick to make changes to your mobile application may also hurt you if you don’t take just a little extra time to complete an effective regression test.

Regression Testing Can Be Challenging

  1. Familiarity breeds contempt. When you’ve seen and tested your mobile applications features and functions every day for the past six months, it’s easy to let your assumptions and urgency take control. This can result in skipping or overlooking some functionality in your haste to release your new mobile application. Using an experienced and trusted third party for your regression testing will insure that nothing is skipped (or assumed to be OK) during your regression testing. “Once over lightly and quickly” is not a good regression testing strategy!
  2. Lack of test documentation. Mobile applications tend to be smaller than web applications and good test documentation is usually the first casualty. And no, your mobile application doesn’t necessarily need a full set of ISO compliant test documentation. But, a decent list of test scenarios and use cases can help you complete your regression testing quicker and with a much higher (and measurable) level of quality and customer delight. An experienced third party software test engineer can quickly and easily help you build and maintain these test documents as a natural part of helping you regression test your mobile application.

Regression testing is simple but not always easy if you aren’t an experienced software test engineer. But, getting help from a professional, at least the first couple times, can go a long way to helping you release your mobile application faster, better and cheaper.

Mobile Application Cross Device Testing

Your mobile application might be used on a new iPhone or an Android phone several years old. Almost all mobile devices behave slightly differently and the difference in behaviors between iOS and Android can be significant. If you fail to test your mobile application on a variety of mobile devices, you are inviting a catastrophe.

There are two basic methods available for cross device testing. You should consider the pros and cons of both before specifying what mobile application testing services to obtain.

Real Mobile Devices and Operating Systems

Real devices provide the best mobile application testing results since you are testing your application on the actual device. But, Real Mobile Devices are expensive to acquire and maintain. Real Mobile Devices are also slightly more time consuming to test on as they require physical handling. Finding a sufficient variety and availability of Real Mobile Devices is a big challenge as new devices and mobile operating systems are released and updated frequently – and this makes the process of building and maintaining a library of mobile devices very expensive.

Mobile Device Emulators

Emulators are usually on-line services where you can load your mobile application on a variety of specific virtual or emulated mobile devices with specific operating systems and versions. Mobile Device Emulators are very handy but have some distinct challenges. Mobile Device Emulators work well for basic functionality but are seldom useful if hardware functionality testing (GPS, Cellular Vs Wifi Networks or Device rotation) is needed to test your mobile application.

But, We Think There is a Better Way

The TESTCo Blended XDT (Cross Device Testing) – at TESTCo, we take a blended approach to using Real Mobile Devices and Mobile Device Emulators. We will help you analyze your expected customer device usage and the current market share of each mobile device and operating system and produce a matrix that compares your testing needs against Real and Emulated devices. We use this to build a testing strategy that optimizes for primarily Real Mobile Device Testing with a portion of Emulator Testing so that we can give you the highest confidence that your mobile application will work flawlessly on the devices that your customers use.

To Be Continued

In the coming weeks I will shed light on the five other types of mobile application testing so you can make smarter testing decisions. In the meantime, check out this post if want tips on how to select a mobile application testing company.

If you can’t wait for me to finish this post (hey, I can’t write all day, I have a business to run), call me (888-254-9709), or request a call back using the green button on this page. I’m happy to answer your questions.

Share This: