Académique Documents
Professionnel Documents
Culture Documents
WebSphere
IBM Software
WebSphere
IBM Software
Contents
1.
1.1.
1.2.
1.3.
1.4.
Overview ............................................................................................................................................5
Exploring IBM MQA Bug Reporting Capabilities .........................................................................6
Test the application and report any bugs .........................................................................................6
Reporting a bug ...............................................................................................................................9
Instructor Demonstration ...............................................................................................................15
Summary .......................................................................................................................................16
A.
Notices..................................................................................................................................17
B.
Trademarks and copyrights ..................................................................................................19
Contents
Page 3
IBM Software
Page 4
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 potential
application crashes without requiring user actions. This lab demonstrates the basic pre-production
capabilities. 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 crashes
that 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 the
development team.
All reported bugs or crash reports will be represented on the MQA dashboard which the instructor can
show to the class in the second portion of the exercise.
Introduction
The Android Virtual Device is a feature of the Android Developers SDK. To simplify the exercise, the
IBM team has pre-defined and instantiated the AVD for the purposes of this lab exercise. While it is
possible 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 testers 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 reporting
service. IBM MQA supports both the shake gesture as well as the use of the Android notification service
to 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, your
credentials need to be added to the Demo Space. Please review the Instructor Guide for instructions on
how to do this few days BEFORE you are scheduled to conduct the lab.
Page 5
IBM Software
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
Page 6
IBM Software
Important!
You may run into a condition where there is not available
space to launch the AVD. If the AVD doesnt 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, please
ask the instructor for assistance.
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 let
go. This will unlock the AVD and bring you to a screen that looks like the following.
Page 7
IBM Software
Page 8
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 can
be identified as the specific user when reporting any bugs or other feedback. Once you have
indicated who you are, the application will present its initial screen.
Page 9
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 doesnt 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 and
drag 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 virtual
devices.
Click anywhere within the notification to bring up the MQA reporting service.
Page 10
IBM Software
Because you want to report a bug, click on the Report a Bug image. If you simply want to
provide feedback, you can click on the Give Feedback image instead. Once you opt to report a
bug, the following screen will be presented.
Page 11
IBM Software
Note that MQA has automatically captured a screen image of the application screen that you
were viewing when you asked to report a bug. Because you want to be clear with what you think
is 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 dont 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 youre done, click on the
Done button.
Page 12
IBM Software
After editing that screenshot, you will be back at the Report a bug main screen as below.
Page 13
IBM Software
Should you have other screenshot captures that you would like to add to the bug report, you can
include 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 look
something like this. Click on the Send button to submit your bug report.
Page 14
IBM Software
After submitting your bug report, youll 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. If
desired, 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 could
help improve the testing cycle, and the development cycle as a whole. Consider how this might
reduce any miscommunications between testers and the development team as well as how it
might compress the overall application delivery time.
Page 15
IBM Software
1.4
Summary
Congratulations. You have successfully experienced some of the key pre-production benefits of using
IBM 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 MQA
service 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 additional
environment 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.
Page 16
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 that
only 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 this
document. The furnishing of this document does not grant you any license to these patents. You can
send license inquiries, in writing, to:
Page 17
IBM Software
been made on development-level systems and there is no guarantee that these measurements will be
the same on generally available systems. Furthermore, some measurements may have been estimated
through 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 and
cannot 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 of
those 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 illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. 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 programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in 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 all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs.
Page 18
IBM Software
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 its
subsidiaries 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/or
its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other
countries, 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.
Page 19
NOTES
NOTES
NOTES
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 IBMs 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.