IBM MobileFirst Platform 7.0 POT InApp Feedback V0.1

8/20/2019 IBM MobileFirst Platform 7.0 POT InApp Feedback V0.1

1/22

IBM Software

WebSphere An IBM Proof of Technology

Mobile Quality Assurance

InApp Feedback

Lab Exercises


2/22

IBM Software

WebSphere An IBM Proof of Technology


3/22

IBM Software

Contents Page 3

Contents

Overview ............................................................................................................................................ 5 1. Exploring IBM MQA Bug Reporting Capabilities ......................................................................... 6

1.1. Test the application and report any bugs ......................................................................................... 6

1.2. Reporting a bug ............................................................................................................................... 9 1.3. Instructor Demonstration ............................................................................................................... 15 1.4. Summary ....................................................................................................................................... 16

A. Notices .................................................................................................................................. 17 B. Trademarks and copyrights .................................................................................................. 19


4/22

IBM Software

MobileFirst Platform 7.0 Proof of Technology – MQA Lab Page 4

"#$% &'() $*")*"$+*',,- ,)." /,'*0


5/22

IBM Software


Overview

The purpose of this lab exercise is to introduce the student to the value of using IBM Mobile Quality Assurance (MQA) in the overall development life cycle of a mobile application. MQA supports a simple

process for instrumenting and deploying a mobile application in the pre-production testing cycle. MQA

can also provide significant value for production deployments to capture and report on potentialapplication crashes without requiring user actions. This lab demonstrates the basic pre-productioncapabilities. The student will launch an appropriate Android Virtual Device (AVD) where the application

under development has already been installed. The application itself has been instrumented with MQA

so the user can easily report any bugs, or other usability issues. Additionally, any application crashesthat may occur will automatically be intercepted and diagnostic data to help identify the cause of the

crash will be uploaded to the MQA management interface for further review and analysis by thedevelopment team.

All reported bugs or crash reports will be represented on the MQA dashboard which the instructor canshow to the class in the second portion of the exercise.

Introduction

The Android Virtual Device is a feature of the Android Developer’s SDK. To simplify the exercise, the

IBM team has pre-defined and instantiated the AVD for the purposes of this lab exercise. While it ispossible to install the application file (apk) on a real mobile device, the use of the AVD makes it easier for

the student to experience the value of MQA from a tester ’s perspective. The class instructor may

optionally install the application file on a real Android device to demonstrate the tester experience using

a real device.

Note: Please note that performance of the AVD is generally not very good, and due to limitations,

several capabilities present on real devices are not available through the AVD interface. In particular, the

AVD does not support the “shake gesture” which is the default mechanism for invoking the bug reportingservice. IBM MQA supports both the shake gesture as well as the use of the Android notification serviceto quickly and easily access the bug reporting activity within the application.

IMPORTANT NOTE TO THE INSTRUCTOR: In order to demonstrate the results of your MQA activity to

the lab participants, you need to be able to log into the Demo Space in Bluemix. To do so, yourcredentials need to be added to the Demo Space. Please review the Instructor Guide for instructions onhow to do this few days BEFORE you are scheduled to conduct the lab.


6/22

IBM Software


Exploring IBM MQA Bug Reporting Capabilities

In this lab, you will launch the instrumented IBM Bank mobile application that has been pre-installed on

an Android Virtual Device (AVD). The application will “connect” you to a live instance of IBM MQA

running in the IBM Bluemix cloud. The live session will allow you to report any feedback or bugs that you

encounter while using the application. Each time you connect to the MQA server will be a uniquesession. These sessions, along with the user identity you use when connecting to MQA provides data forthe test coordinator to catalog comments and bugs and allows the coordinator (or developers) to contact

you for additional details should that become necessary. You will be able to test the current version ofthe IBM Bank application and report any bugs or other concerns. All bugs are automatically uploaded to

the MQA service and made available for the QA team to review. The team can then forward all valid

reports to the development team for remediation.

The instructor will connect to the IBM Bluemix dashboard to share the bug reports with the class.

Test the application and report any bugs

In this section, you will test the application in its current state and provide feedback/bug reports for the

developers to review before the next sprint.

Starting the Android Virtual Device Emulator

From the Windows 7 desktop, start the MQA equipped AVD emulator by performing the following steps:

Locate the Start MQA AVD icon in the MobileFirst Platform folder and double-click it to launchthe AVD.

Alternatively, you can open a DOS Window and type the following command (without the quotes)

to start the AVD. ‘ C:\I\android-sdk\tools\emulator-x86.exe -avd MQA’

‘ C:\I\android-sdk\tools\emulator-x86.exe -avd MQA’


7/22

IBM Software


Within 30 seconds, you should see the Android Virtual Device start. When it is finished loading,

you will see the following image.

Place the mouse on the lock symbol and drag it to the right edge of the emulator screen and letgo. This will unlock the AVD and bring you to a screen that looks like the following.

Important!

You may run into a condition where there is not available

space to launch the AVD. If the AVD doesn ’t start up within

30 seconds, you will need to run disk cleanup on the C drive.If you are not familiar with how to accomplish this, pleaseask the instructor for assistance.


8/22

IBM Software


You can now complete the remainder of the lab.


9/22

IBM Software


1.2 Reporting a bug

Double click on the IBMBankApp icon to launch it. You will first see the application “splash”

screen and then after a short delay, you will be greeted with the MQA session login screen.

There may be a number of valid userids in the list.

Click on the AVD “back” button indicated by the red arrow in the above images. This tells the

MQA service that you will not be reporting as one of the known users for this session. Normally,

all test users would be represented int he list and you would select the proper entry so you canbe identified as the specific user when reporting any bugs or other feedback. Once you have

indicated who you are, the application will present it’s initial screen.


10/22

IBM Software


Oops! There is an error in the text contained in the Log on button. It happens to be misspelled.You want to submit this as a bug. If you were using a real device (instead of a virtual one), you

could simply shake the device to initiate a bug report. Since the AVD doesn’t support the shake

gesture, the MQA client automatically places a notification icon to represent the background bug

reporting service. Notice the IBM MobileFirst icon in the Notification area of the device. Click anddrag from within the Notification area downward towards the bottom of the virtual device to view

how you can report a bug or provide feedback. This method works on both real and virtualdevices.

Click anywhere within the notification to bring up the MQA reporting service.


11/22

IBM Software


Because you want to report a bug, click on the Report a Bug image. If you simply want toprovide feedback, you can click on the Give Feedback image instead. Once you opt to report a

bug, the following screen will be presented.


12/22

IBM Software


Note that MQA has automatically captured a screen image of the application screen that youwere viewing when you asked to report a bug. Because you want to be clear with what you thinkis in error, you can edit the screen capture and annotate it. Click on the screen image to bring up

the image annotation editor.

Note the tools across the bottom of the screen. The leftmost tool is a pen/brush. You can use it

to mark the screen as you wish. The middle tool is the “blur ” tool. Use this to hide any

personal/confidential data which you don’t want to share. The rightmost tool is the eraser.

Clicking on it will remove all annotations which have been made to the image. Spend a few

moments and make as many annotations as you would like. When you’re done, click on the

Done button.


13/22

IBM Software


After editing that screenshot, you will be back at the Report a bug main screen as below.


14/22

IBM Software


Should you have other screenshot captures that you would like to add to the bug report, you caninclude them by clicking on the + image and selecting additional images. Or, you can use the

device keyboard to type in any notes you would like to include which will help the developer

understand your concern. Use the laptop keyboard to type in some text. Your screen will looksomething like this. Click on the Send button to submit your bug report.


15/22

IBM Software


After submitting your bug report, you’ll be brought back to the same screen you were viewing

prior to submitting the bug report. At this point, you are done with your portion of the exercise. Ifdesired, you may explore other parts of the application or submit additional bugs/feedback

reports.

1.3 Instructor Demonstration

The remainder of this exercise will be an instructor led demonstration. The instructor will show

the class participants the collection of bug reports which were submitted during this activity.During the demonstration, pay close attention to the environment details which were

automatically uploaded to the MQA server.

Take a few minutes and discuss how having this type of service within your organization couldhelp improve the testing cycle, and the development cycle as a whole. Consider how this mightreduce any miscommunications between testers and the development team as well as how it

might compress the overall application delivery time.


16/22

IBM Software


1.4 Summary

Congratulations. You have successfully experienced some of the key pre-production benefits of usingIBM Mobile Quality Assurance as part of your mobile application development lifecycle. By completing

this exercise, you were able to see how simple it is to establish a test session with a configured MQAservice and report bugs and/or provide feedback to the development team. You also were able to view

the dashboard which is available to the QA team and developers and the rich amount of additionalenvironment data which is automatically captured with each bug report. Moreover, the dashboard

provides information as to the number of sessions established and the number of bug reports within a

given period of time and any trends associated with those reports.


17/22

IBM Software


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available in

your area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program, or

service that does not infringe any IBM intellectual property right may be used instead. However, it is the

user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You cansend license inquiries, in writing, to:

$/1 23456784 89 ,365:;3:<

$/1 =84>84?738:

*847@ =?;7A5 243B5

'4C8:DE *- FGHGIJFKLHMN%N'N

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

$/1 O84AP "4?P5 ';3? =84>84?738:

,365:;3:<

QJRF S8>>8:


18/22

IBM Software


been made on development-level systems and there is no guarantee that these measurements will bethe same on generally available systems. Furthermore, some measurements may have been estimatedthrough extrapolation. Actual results may vary. Users of this document should verify the applicable data

for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their

published announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM

products. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without

notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by an

actual business enterprise is entirely coincidental. All references to fictitious companies or individuals are

used for illustration purposes only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributing

application programs conforming to the application programming interface for the operating platform for

which the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms.


19/22

IBM Software


Trademarks and copyrights

"@5 98AA8X3:< 754C; ?45 74?P5C?4D; 89 $:754:?738:?A /T;3:5;; 1?6@3:5; =84>84?738: 3: 7@5 M:375P

%7?75;E 87@54 68T:7435;E 84 Y87@Z

IBM AIX CICS ClearCase ClearQuest Cloudscape

Cube Views DB2 developerWorks DRDA IMS IMS/ESA

Informix Lotus Lotus Workflow MQSeries OmniFind

Rational Redbooks Red Brick RequisitePro System i

System z Tivoli WebSphere Workplace System p

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.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications

Agency which is now part of the Office of Government Commerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel

SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the

United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet

Office, and is registered in the U.S. Patent and Trademark Office.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, othercountries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp.

and Quantum in the U.S. and other countries.


20/22

OT S


22/22

OT S

The information contained in these materials is provided for

informational purposes only, and is provided AS IS without warranty

of any kind, express or implied. IBM shall not be responsible for any

damages arising out of the use of, or otherwise related to, these

materials. Nothing contained in these materials 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 these materials to IBM products,

programs, or services do not imply that they will be available in all

countries in which IBM operates. This information is based on

current IBM product plans and strategy, which are subject to change

by IBM without notice. Product release dates and/or capabilities

referenced in these materials 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.

IBM, the IBM logo and ibm.com are trademarks of International

Business Machines Corp., registered in many jurisdictions

worldwide. Other product and service names might be trademarks of

IBM or other companies. A current list of IBM trademarks is

available on the Web at “Copyright and trademark information” at

www.ibm.com/legal/copytrade.shtml.

Documents

IBM MobileFirst Platform 7.0 POT InApp Feedback V0.1