Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IBM Mobile Quality Assurance - Open Beta Study Group Session 2

2,019 views

Published on

Viewing Crashes and Bug Reports

Published in: Technology
  • Be the first to comment

  • Be the first to like this

IBM Mobile Quality Assurance - Open Beta Study Group Session 2

  1. 1. IBM Mobile Quality Assurance Continuously deliver quality mobile apps – MQA Study Group – 1 November 2013 Host: Roger Snook, WorldWide Enablement Leader: Mobile, SOA & Design +1.703.943.1170, RCSnook@us.ibm.com Session 2: Viewing crashes and bug reports (Session 1 Slides and Recording: http://ibm.co/174C6ug) © 2013 IBM Corporation
  2. 2. 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 benchmarks in 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. 2 #IBMMobile © 2013 IBM Corporation
  3. 3. Facts: Organizations that effectively leverage software development outperform their competitors... 86 % of companies believe software delivery is important or critical of those who leverage software delivery today yet few are able to deliver it effectively 69 25 % leverage software delivery effectively today % outperform those who don’t The same percentage of mobile developers who claim Testing and Quality Assurance is in their top 5 concerns… SD Times: “More than half of organizations are building mobile applications” http://www.sdtimes.com/link/36553 Also claim they are challenged with developing applications as quickly as management wants Source: “The Software Edge: How effective software development drives competitive advantage,” IBM Institute of Business Value, March 2013 3 #IBMMobile © 2013 IBM Corporation
  4. 4. Mobile Quality automation fundamental to a DevOps Lifecycle Continuously deliver high-quality mobile applications (HTML5, hybrid and native) and support multiple mobile operating environments and devices with the simplicity of a single, shared code base DevOps Lifecycle Customers Business Owners Development/Test Operations/Production Systems of Interaction Continuous Innovation, Feedback and Improvements Develop and Test Worklight IBM Mobile Quality Assurance Rational Test Workbench Release and Deploy Best Practices Ecosystem Plan and Measure Monitor and Optimize Judge mobile application quality and customer readiness across multiple dimensions, to deliver apps that better meet customer expectations 4 Automate and orchestrate the delivery pipeline for IT infrastructure and the mobile app, reducing cycle times to respond faster to feedback #IBMMobile © 2013 IBM Corporation
  5. 5. Updated xx-xx-12 Introducing IBM Mobile Quality Assurance (beta) Continuously deliver high quality mobile applications What’s New • End user feedback and quality metrics available at every stage of development IBM Mobile Quality Assurance (beta) • App quality assurance in a fragmented and complex environment  Features/Business Value • Evidence-based prioritization – enable business and IT to collaborate on mobile strategy and user experience • Over the air app distribution – get the latest in the hands of testers as soon as it is available • Frictionless bug reporting – spend every minute on testing latest and greatest builds, not the hassles • In-app crash reporting – rapid understanding of why an app fails • Sentiment analysis – mine app ratings and reviews to extract actionable feedback before they go viral(coming soon) Client Benefits 5 • Improve mobile app quality with holistic visibility into user experience, including bugs, crashes, feedback, and user sentiment • Proactively manage quality risks through rapid assessment of issues and reduced cycle time #IBMMobile ”What you are talking about doing is fantastic. You have a very powerful approach here and it will drive a lot of what people will want to do in the market” © 2013 IBM Corporation
  6. 6. Mobile Quality Assurance features that support the Use Cases Session 2 Focus: Viewing crashes and bug reports User Feedback Crash logs 4 Crash log reporting Bugs vs. Crashes Bugs LOB/Digital Marketer Developer Coming soon 5 Sentiment Analysis 1 Over the air build distribution 2 Quality Dashboard with Sentiment Analysis 6 Tester In app bug reporting End Users 3 In app user feedback Builds #IBMMobile © 2013 IBM Corporation
  7. 7. Just how long does it take to fill out a good bug/crash report? Bug details SHOULD include: •Device maker & model •OS & version •Carrier & connection speed •Battery life & resolution •Repro steps & screenshot BEFORE MQA 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 7 #IBMMobile Crash details SHOULD include: •Stack trace •Logs AFTER MQA 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! © 2013 IBM Corporation
  8. 8. In app bug reporting 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 Enables developers to receive bug reports 8 #IBMMobile © 2013 IBM Corporation
  9. 9. In app bug reporting View bug reports from three places in platform •MQA Overview •Bug Menus •Sessions Overview Information and Action •Bugs List •Session Details Page •How to Report a Bug •Manage Notifications Enables developers to receive bug reports 9 #IBMMobile © 2013 IBM Corporation
  10. 10. Crash log reporting When your app crashes, IBM MQA logs the event IBM MQA captures the crash details •Device maker & model •OS version •Carrier & connectivity •Battery life •Stack trace •Logs IBM MQA aggregates all crashes into an easy-to-use reporting UI Enables developers to know when and why crashes occur 10 #IBMMobile © 2013 IBM Corporation
  11. 11. Crash log reporting View crashes from three places in platform •IBM MQA Overview •Crash Menus •Sessions Overview IBM MQA provides •Crash Lists •Crash Details •Session Details •Manage Notifications •Live Reports Enables developers to know when and why crashes occur 11 #IBMMobile © 2013 IBM Corporation
  12. 12. IBM Mobile Quality Assurance Focus: Viewing Crashed and Bug Reports 12 #IBMMobile © 2013 IBM Corporation
  13. 13. IBM Mobile Quality Assurance Open Beta Study Group: http://ibm.co/174C6ug 13 #IBMMobile © 2013 IBM Corporation
  14. 14. Your Study Group Action Items for Today: 1. Take Brief Survey – Your feedback helps! (Coming soon to your inbox) 2. Watch the *new* MQA Tutorial Video 3. Try It: MQA Open Beta – click on this button from the landing page: 14 #IBMMobile © 2013 IBM Corporation
  15. 15. Ways to get started with IBM MobileFirst 1 2 3 Tools and Technologies for MobileFirst Developers: http://www.ibm.com/developerworks/mobile/ Take part in the IBM Mobile Quality Assurance open beta: http://ibm.co/174C6ug Read the CTO Mobile Frontier Blog: https://www.ibm.com/developerworks/community/blogs/mobileblog Our Next Session: IBM Mobile Quality Assurance Study Group Session 3: Connecting mobile app end-users and the developer environment, Nov 8, 2013 9:00AM https://events.na.collabserv.com/register.php?id=b6855e07bb&l=en-US 15 Further Study: Mobile Learning Circle (coming soon) © soon) #IBMMobile Mobile Testing Product Usage Learning Roadmap (coming 2013 IBM Corporation
  16. 16. 16 #IBMMobile © 2013 IBM Corporation
  17. 17. Legal Disclaimer © IBM Corporation 2013. All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in 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. If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. 17 #IBMMobile © 2013 IBM Corporation

×