Instrumenting your app - part of the study group series.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
IBM Mobile Quality Assurance (Open Beta) Continuously deliver quality mobile apps – MQA Study Group – 8 November 2013
Host: Roger Snook, WorldWide Enablement Leader: Mobile, SOA & Design +1.703.943.1170, [email protected]
Session 3: How to instrument your mobile app to use MQA's time-saving features(Prior Session Slides and Recordings: http://ibm.co/174C6ug - pre-requisite)
Please note – This discussion is about an Open Beta
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Performance is based on measurements and projections using standard IBM benchmarksin a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
How much time do you need to save in your mobile dev cycle?Bug details SHOULD include:•Device maker & model•OS & version•Carrier & connection speed•Battery life & resolution•Repro steps & screenshot
Before MQA:•Manually enter each piece of information•Risk of manual inaccuracy vs time for quality information•Crash detail may require IDE environment to produce (iOS)
•Assertion: 15 minutes per bug/crash report to gather this quality information
User simply shakes their device
1. IBM MQA is activated
2. Bug details are reported in structured manner to RTC
Crashes logged automatically!
Assertion: Estimated time savings nears 15 minutes per bug. Multiply this by how many bugs reported. (i.e. 100 bugs = 25 hours of time saved). This is reporting alone – quality analysis alone is time consuming!
1. Platform / OS / IDE requirementsWhile I chose an Android version, for this exercise, I used the
Worklight Eclipse-plugin IDE.• Worklight® Studio of the IBM Worklight Developer
Edition is supported on the following operating systems:• Windows, Mac OS, Linux (same as RTC)
• You can develop IBM Worklight applications with iOS environments on any of these operating systems. However, due to restrictions set by Apple, you can compile an iOS project only on a Mac OS.
• When used on a Mac OS, the Worklight Studio integrates with Xcode (the iOS development environment).
• Getting Started with Worklight 6• Set up your Android development environment
• Install the Android SDK• Install the Android Development Tools plug-in for
Eclipse• Deploy to an Android device
• Setting up a device for development
Studio
IBMers can access an IBM-licensed preconfigured environment here instructions included.
IBMers can access an IBM-licensed preconfigured environment here instructions included.
Depending on what capabilities you want to provide, there are two different libraries to download:
1. Pre-Production (selected for this session)Using the Pre-Production Library - How to configure IBM Mobile Quality
Assurance for use in your application when it is still in QA and in the hands of your testers. The pre-production is ideal for when your application is still in testing with a small group of people.
By default, testers using your app with the pre-production library will be asked to login to the app so that IBM Mobile Quality Assurance can tell you who reported which bugs and issues.
2. ProductionUsing the Production Library - How to configure IBM Mobile Quality
Assurance for use in your application after it has launched and is in the hands of your customers.
Reports all data anonymously AND respects your users' privacy by gathering fewer details along with the logs, session data, and crash reports from your app.
When bugs are identified, user simply shakes their device
1. IBM MQA is activated
2. Bug details are reported in structured manner to RTC
Bug details include
•Device maker & model
•OS & version
•Carrier & connection speed
•Battery life & resolution
•Repro steps & screenshot
•If you are using a “softphone” / emulator / AndroidVM – swipe down instead of shake.•Sample apps are available on MQA•IBMers can test a pre-built MQA Worklight app here (look for the APK).