Comprehensive Report on User Acceptance Testing of Mobile Applications

This report provides an in-depth analysis of User Acceptance Testing (UAT) for mobile applications. It highlights the importance of UAT in ensuring that software meets the needs of real users and functions correctly in real-world scenarios. The report contrasts UAT with other types of software testing, such as unit and integration testing, emphasizing its focus on the user's perspective and experience. It describes the UAT process, including alpha and beta testing, and mentions tools like Appium, Calabash, Robotium, and Selendroid. The report also identifies the key stakeholders involved in UAT, namely users, the software development company, and the client, emphasizing the contractual and practical implications of successful UAT. The report concludes by stressing the necessity of UAT to avoid disputes during the maintenance phase and to prevent potential adverse effects on the client's business functions, underscoring the significance of user validation before software delivery.

Running head: USER ACCEPTANCE TESTING FOR MOBILE APPLICATIONS
User Acceptance Testing for Mobile Applications
Your Name (First M. Last)
School or Institution Name (University at Place or Town, State)
1

USER ACCEPTANCE TESTING FOR MOBILE APPLICATIONS
Abstract
Software is a complex system and handles life- and mission-critical activities e.g. medical
systems, space exploration, deep sea equipment. Also, billions of dollars change hands daily on
the foundation of software e.g. banking, insurance, stock markets, and other financial
institutions. Also, many other activities which are less consequential also depend on software
like entertainment, communication, and others. The software is everywhere, and there is hardly
any human activity which is not founded on or impacted by software. The software, however, is
not a reliable system in general. The history of software is littered with losses in lives and money
due to software bugs. Thus, the importance of verifying that software meets the requirements.
This process of software development is called testing. Software testing is of many types, and
each intends to test the specific components or aspects of the software. Some of the types are unit
testing, integration testing, functional testing, system testing, stress testing, performance testing,
usability testing, and acceptance testing. This paper is about acceptance testing, also referred to
as user acceptance testing, with a focus on mobile applications. The focus of tests other than user
acceptance tests are on the small facets of the software and ensuring that it meets the
performance requirements, compatibility of hardware and software requirements and that the
individual parts of the software work as expected. In the broader picture, such tests are relatively
of little importance to the user. To consider the users' point-of-view, user acceptance testing is
performed at the end of the software development cycle, and the passing of this test is a
requirement before the client accepts the software. The focus of user acceptance testing is not in
the specifications, but the users. As an illustration of user acceptance testing contrasting with the
other types of testing, consider a user of a social networking mobile application. That user is
concerned that his Like on a photograph is registered successfully, and the owner of that photo
2

USER ACCEPTANCE TESTING FOR MOBILE APPLICATIONS
and the tagged people are updated instantly. He may not be that interested in the technicalities
that make this action happen, and the tests that go into ensuring that his action will be done
successfully. Thus, the goal of user acceptance testing is to ensure that the software meets the
requirements of real users in real-world situations. This verification may be achieved by a team
of testers representing the actual user (Alpha Testing), or with the actual users themselves with
an understanding that the aim of using the software is to test it (Beta Testing). Tools that are
available to help in the process of user acceptance testing include Appium, Calabash, Robotium,
Selendroid. Some of these work across platforms, while others are specific to platforms like
Android, or iOS. The stakeholders in a user acceptance testing are the users (or the group
representing users), the company that developed the software, and the paying client. Without a
pass in this test, the contract between the business and the client will not be fulfilled, and thus the
delivery of the software (and the pending payments) for it will not be done. User acceptance
testing should not be skipped for the reason that the developing company is delivering a solution,
and not some source code files only. The acknowledgement by users that the software meets
their requirements before the final delivery is accepted is essential to a dispute-free maintenance
period. It is possible that in the case of skipping the testing, incorrectly implemented
requirements will adversely affect the business functions of the client.
Keywords: software, testing, user acceptance testing, mobile applications
3