IBM Mobile Quality Assurance

Continuously deliver quality mobile apps – MQA Study Group – 1 November 2013
Host: Roger Sno...
Please note – This discussion is about an Open Beta
IBM’s statements regarding its plans, directions, and intent are subje...
Facts: Organizations that effectively leverage software development
outperform their competitors...

86

%

of companies b...
Mobile Quality automation fundamental to a DevOps Lifecycle
Continuously deliver high-quality mobile applications (HTML5, ...
Updated xx-xx-12

Introducing IBM Mobile Quality Assurance (beta)
Continuously deliver high quality mobile applications

W...
Mobile Quality Assurance features that support the Use Cases
Session 2 Focus: Viewing crashes and bug reports
User Feedbac...
Just how long does it take to fill out a good bug/crash report?
Bug details SHOULD include:
•Device maker & model
•OS & ve...
In app bug reporting
When bugs are identified, user simply
shakes their device
1. IBM MQA is activated
2. Bug details are ...
In app bug reporting
View bug reports from three places in
platform
•MQA Overview
•Bug Menus
•Sessions Overview
Informatio...
Crash log reporting
When your app crashes, IBM MQA logs
the event
IBM MQA captures the crash details
•Device maker & model...
Crash log reporting
View crashes from three places in
platform
•IBM MQA Overview
•Crash Menus
•Sessions Overview
IBM MQA p...
IBM Mobile Quality Assurance
Focus: Viewing Crashed and
Bug Reports

12

#IBMMobile

© 2013 IBM Corporation
IBM Mobile Quality Assurance Open Beta Study Group: http://ibm.co/174C6ug

13

#IBMMobile

© 2013 IBM Corporation
Your Study Group Action Items for Today:
1. Take Brief Survey – Your feedback helps!
(Coming soon to your inbox)
2. Watch ...
Ways to get started with IBM MobileFirst

1
2
3

Tools and Technologies for MobileFirst Developers:

http://www.ibm.com/de...
16

#IBMMobile

© 2013 IBM Corporation
Legal Disclaimer
© IBM Corporation 2013. All Rights Reserved.
The information contained in this publication is provided fo...
Upcoming SlideShare
Loading in …5
×

IBM Mobile Quality Assurance - Open Beta Study Group Session 2

1,958 views

Published on

Viewing Crashes and Bug Reports

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,958
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
48
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • {"5":"SPEAKER NOTES PRESENTERS may want to delete speaker notes prior to presenting to clients/external audience\nOffering Name: IBM Mobile Quality Assurance\nOffering Description: IBM Mobile Quality Assurance provides everything an organization needs to deliver high quality mobile apps, bringing together in one place, user feedback, app performance, test results, bug reports, and sentiment analysis to drive prioritization and development of mobile app updates that address issues before they affect reputation.\nTarget Market/Industries: All\nWhat is New News? This is a brand new SaaS offering, being delivered as a free open beta for all organizations needing to deliver the highest quality mobile apps possible.\nClient Needs Addressed:\nMaking sure that the app design meets the end user need and achieves the business objectives\nVerify that the app works correctly in a fragmented (complex) environment of mobile devices and operating systems\nValue Proposition: (Describe how the offering helps the consumer improve operations, deliver/access new capabilities, increase revenues/profits, perform roles more efficiently, perform functions previously not possible )\nIBM Mobile Quality Assurance provide line of business professionals with insightful and streamlined quality feedback and metrics, enabling them to dramatically improve decisions on mobile app priorities and investments. \nIBM Mobile Quality Assurance equips mobile app development teams with everything they need to deliver the highest quality mobile applications through rapid inclusion of quality feedback throughout the development cycle.\nKey Benefits: (for Launch Theme)\nOver the air app distribution – get the latest in the hands of testers as soon as it is available\nIn-app crash reporting – rapid understanding of why an app fails\nIn-app user feedback – frictionless way to determine user likes and dislikes\nSentiment analysis – mine app ratings to respond to issues before they go viral\nCompetitors & Differentiation: (List appropriate competitors and key differentiation from IBM vs. Competitors)\nTestFlight\nCrittercism\nBugsense\nJira Mobile Connect\nHockeyApp; Zubhium\nDifferentiation: \nMobile specific aggregated feedback for rapid assessment of quality and prioritization of effort\nIncorporate end user feedback and quality data at every stage of development\nAssess how the app behaves across many combinations of devices, diverse network conditions, and with back end service\nSparklers: (Measurable or significant performance/capability facts or proof points)\nbullet\nbullet\nQuote is from Ken Parmalee, Gartner Research\n","6":"So, with those pain points in mind, our initial tech preview will focus on five key use cases… \nFor the DEVELOPER: Over-the-Air Build Distribution – Developers can distribute new builds over-the-air to real devices for testing purposes; automatically ensures that testers have the latest build\nFor the TESTER: In-App Bug Reporting – Bug reports can be submitted directly from the app; available for pre- and post-launch; importantly, this also saves the contextual information around the bug, packaging up what is needed (like crash logs) to make it easy to get them to the developer\nFor the END USERS: In-App User Feedback – User feedback can be submitted directly from the app, enabling developers to easily spot trends, discover issues and receive new ideas from end users; also\n…Crash Reporting – Automated, real-time crash reports are filtered by OS version, device and other parameters; available for pre- and post-launch\nFor the LOB / Digital Marketer: Sentiment Analysis, providing these users with details from the app stores on user feedback for their impressions or “sentiment” regarding mobile applications; this is based on crawling through every rating and review and then boiling it down to a single score as a means to measure user satisfaction… this will allow clients to monitor and measure how their mobile apps are performing in the eyes of users.\n","12":"Author Note: Optional Rational DEMO slide. Available in English only.\n","13":"Author Note: Optional Rational slide. Graphic is available in English only.\n","14":"Marketing is the science of choosing target markets through market analysis and market segmentation, as well as understanding consumer buying behavior and providing superior customer value. Source: http://en.wikipedia.org/wiki/Marketing\n","3":"Main Point: We know organizations have a gap between the software delivery capabilities they need to succeed and the ones they have in house currently. Successful organizations know that when they improve their abilities in this area, they increase their success. \nIn fact a recent IBV study where organizations self-reported that... Insights from 435 executives in 58 countries, spanning 18 industries\n85% realize and reported it is important to critical\nOnly 25% say they are able to fully leverage software delivery effectively \nSo there is a gap -- but when companies that can close the resulting execution gap stand to benefit. \nAlmost 70 percent of the companies currently leveraging software development for competitive advantage outperform their peers from a profitability standpoint\nTRANSITION – so there is a huge opportunity for our clients to close that gap…let’s move to the next slide and talk about how\n--------------------------------------------------------------------------------------------------\nNote: Outperformers were determined by a self-assessment of profitability against peers in the industry, ranging from 1 (Significant underperformers) to 5 (Significant outperformers) Significant outperformers were ranked as a 5, Average performers a 3-4 and Underperformers 1-2\nnew Rational/WebSphere IBV Study "The Software Edge - How effective software development drives competitive advantage" \nThis study examined the correlation between software delivery competency and industry competitive advantage\nInsights from 435 executives in 58 countries, spanning 18 industries\nRoles included executives at director level and above in IT and other software organizations\nSoftware delivery refers to all areas of development, operations, and support within IT and other development / engineering organizations\n“There was 54% of the companies who said they believe software is critical and 32 percent who called it moderately important – so that’s 86 percent of the respondents say software is either critical or moderately important and that points to the need for better tooling for software development and delivery.” said Randy Newell, director of capabilities marketing for IBM Software Group with a focus on the Rational brand.\n","15":"IBM Mobile Quality Assurance Overview and Use Cases (Mobile Study Group Session 1)    Oct 25, 2013    9:00 AM - https://events.na.collabserv.com/register.php?id=89922788f7&l=en-US \nIBM Mobile Quality Assurance Study Group Session 2: Viewing crashes and bug reports    Nov 1, 2013    9:00 AMhttps://events.na.collabserv.com/register.php?id=44a9a6a4dd&l=en-US \nIBM Mobile Quality Assurance Study Group Session 3: Connecting mobile app end-users and the developer environment    Nov 8, 2013    9:00 AMhttps://events.na.collabserv.com/register.php?id=b6855e07bb&l=en-US \nIBM Mobile Quality Assurance Study Group Session 4: Over the air build distribution    Nov 15, 2013    9:00 AMhttps://events.na.collabserv.com/register.php?id=6ab12a9957&l=en-US \nIBM Mobile Quality Assurance Study Group Session 5: Mobile user sentiment and analytics    Nov 22, 2013    9:00 AMhttps://events.na.collabserv.com/register.php?id=bdba44a231&l=en-US \n"}
  • 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

    ×