Nope. No way.
But for an old guy like me who actually went through the Y2K "fun", I have to wonder if we're getting any closer to the tipping point of developers leveraging professional testers instead of the "continuous dev/test/deliver heroism" when our platform code changes? While there are good articles on making it "easy" to migrate to iOS 8 (and probably tons more on all the variants of Android), it just begs the question, who is testing all of that mobile app functionality ... again and again and again for each OS update? Regression testing addresses this specific problem, especially if you're just trying to react quickly to get your newly rebuilt app out for iOS 8.
But regression testing can be a chore UNLESS you have:
- Documented test plans
- Documented test steps
- Some way to automate those test steps (who has time to waste doing all that manually????)
But forget all of that "professional testing talk" for a moment, gosh, we're just building a mobile app after all. Maybe I'm interested in doing a little on-device testing "in the wild", or sending the app out as-built and capturing any crashes that occur automatically, or simply letting the user report some feedback on the app without flaming me on the appstore ratings. Fortunately, for those building iOS 8 apps, you can do exactly those things with MQA.
Compile in the iOS 8-ready SDKs of Mobile Quality Assurance and you'll get:
- In-app Bug Reporting - shake the phone to report a defect in seconds instead of .... maybe ....entering a decent defect report into your favorite workitem system (such as offered in DevOps Services for Bluemix or Rational Team Concert - both of which can be integrated into MQA!).
- Automated Crash Reporting - again, I'll show my age....do you remember "Dr. Watson" for Windows apps? It was awfully nice to get a crashdump - and this feature of MQA gives me lots of useful info about the device and a stack trace to help me pinpoint the problem.
- User Feedback - put a menu option or a quick-tap-link in your app to prompt the user for feedback on the app, rather than wait until it's too late and you get negative ratings and comments in the appstore.
Uh-oh.....my conscience is calling....and it's telling me I should do some regression testing. Mobile apps are here to stay. OS versions will continue to change. What better way to handle that change than with testing. So omitting automated mobile UI testing for a moment, writing, as I mentioned above, documented test plans and steps can be a chore, but so can be the whole management of them! Where do you store that information? This is simply going back to a good principle of a single-source of truth, something that we've been talking about in the 5 ALM Imperatives, and therefore, I'll suggest mobile teams need to be using Rational Quality Manager to better organize, collaborate, communicate, plan and execute tests - even just manual tests, as many are still putting their "toes in the water" on automation for mobile apps.
Finally, let's address mobile UI test automation. The market offerings here are reminiscent of the desktop and web app era - several small companies emerging from building their own tools on projects because the market didn't offer any....or weren't aware of companies like IBM with offerings.....such as Rational Test Workbench (RTW) - which has had mobile UI testing capabilities out for over a year now! In fact, we've recently repackaged this mobile UI testing into a lower-priced offering RTW Mobile Test Edition (RTW MTE), If you've seen me present, I love to refer to "FURPS", a clean "F-word" you can use in the industry to refer to the various kinds of quality dimensions which takes me to my last point: Gartner names IBM a Leader in 2014 Magic Quadrant for Integrated Software Quality Suites!