SOFTWARE TESTING

HOW TO TEST A
MOBILE APPLICATION
Presented by,
Sandhya Prakash P
 Contents

Introduction to Mobile Application

1 Best Practices in Mobile App Testing 6
Testing
Example: Testing an E-Commerce
Types of Mobile App Testing 2 7
App
Mobile App Testing Process 3 Conclusion 8
Tools for Mobile Application
4
Testing

Challenges in Mobile App Testing 5

 Introduction to Mobile
Application
Explanation: Mobile application testing ensures that apps
function correctly on smartphones and tablets, across various
platforms and devices.

Example: Testing an e-commerce app like Amazon to verify

that it works on both Android and iOS, with different screen
sizes.
 Functional Testing

Usability Testing

Performance Testing
Types of Mobile
App Testing Compatibility Testing

Security Testing

Back to Agenda
Regression Testing
 Functional Testing Usability Testing

Definition: Ensures that the app functions Definition: Ensures the app is easy to use and

according to the requirements. user-friendly.

Example: Testing if users can add items to

Example : Checking if the app’s layout is
the shopping cart.
usable for new users.

Software Testing
 Performance Testing Compatibility Testing

Definition: Tests the app's performance under Definition: Ensures the app works across

various conditions.. different devices, OS versions, and screen

resolutions.

Example: Checking how the app behaves

Example : Testing an app on both iPhone 12
under heavy traffic, such as during a sale
and Samsung Galaxy S20.
event.
Software Testing
 Security Testing Regression Testing

Definition: Verifies the app’s security measures Definition: Ensures that new code does not

to protect data. break the existing functionality.

Example: Checking if the app securely

Example : Testing an app after a new update to
handles payment information.
ensure old features still work.

Software Testing
 Test Planning

Test Design

Mobile App Test Execution

Testing Process
Test Reporting

Test closure
Back to Agenda
 Mobile App Testing Process

1.Test 2.Test 3.Test

Planning 2023 Design Execution

 Define the scope,  Design test  Execute the tests

objectives, and cases, scripts, on real devices or
testing and scenarios. emulators.
environment.
 Example: A test  Example: Testing
 Example:
case that checks the login
Deciding which if the user can functionality on
devices, OS successfully log both iOS and
versions, and in. Android.
features to test.
 Mobile App Testing Process

4.Defect 5.Test
Reporting Closure

 Identify and report bugs or  Finalize test results and

issues. report findings.

 Example: A bug where the  Example: Preparing a

app crashes on Android summary report of testing
when opening the settings activities.
page.
  Emulators/Simulators:

Example: Android Emulator for testing

on Android devices without needing
physical devices.

 Real Device Testing:

Tools for Mobile
Testing directly on physical devices for
Application Testing more accurate results.

 Automation Tools:

Appium: For automating functional tests

on Android and iOS apps.

Robot Framework: For automating

mobile testing scenarios.
Challenges in Mobile App
Testing
 Device Fragmentation:
Explanation: There are many device types, screen sizes, and OS versions to consider.
Example: Testing an app on a variety of Android devices with different screen resolutions.
 Network Conditions:
Explanation: Mobile apps behave differently under various network conditions.
Example: Testing app performance on 2G, 3G, and Wi-Fi networks.
 App Updates:
Explanation: Apps are regularly updated, and testing needs to verify that new features don't break existing
ones.
Example: Testing an app after a major update to ensure all functionalities work.
Best Practices in
Mobile App Testing.
Test on Real Devices: Emulators may not replicate real-world
conditions accurately.

Consider User Experience: Focus on usability and smooth

navigation.

Test on Different Network Conditions: Ensure the app works

on both fast and slow networks.

Automate Where Possible: Automation can speed up repetitive

testing tasks.

Test for Battery and Memory Usage: Ensure that the app
doesn’t drain the phone’s battery or consume excessive
memory.
  Functional Testing: Verify product search, adding to cart,
and checkout process.

 Usability Testing: Check if users can easily navigate

through the app and find products.

Example  Performance Testing: Load testing during peak shopping

hours
esting an E-Commerce App
 Security Testing: Ensure secure payment gateway
integration.

 Compatibility Testing: Test on different devices, such as

iPhone, Samsung Galaxy, and Google Pixel.
Functional Testing Scenarios

FS1: Verify that users can successfully register and FS6: Verify that all form fields accept valid inputs and
log in with valid credentials. handle invalid inputs gracefully.
FS2: Check if the system prevents login with FS7: Ensure that role-based access control works
incorrect credentials and displays appropriate error correctly (e.g., admin vs. regular users).
messages. FS8: Validate that all links and buttons perform their
FS3: Ensure that password reset functionality works expected actions.
correctly. FS9: Check if system notifications and alerts are triggered
FS4: Validate that users can create, update, delete, correctly.
and retrieve records as per system requirements. FS10: Ensure integration with third-party services (e.g.,
FS5: Check if the system correctly applies business payment gateway, email service) functions as expected.
rules (e.g., discounts, validation checks).
Usability Testing Scenarios

US1: Check if the system has a user-friendly US6: Check if users can complete key tasks (e.g.,
interface. registration, checkout) with minimal effort.
US2: Verify that navigation is simple and users can US7: Ensure that text, icons, and images are clear,
easily find key features. readable, and displays visually .
US3: Check if the system provides clear and helpful US8: Verify that tooltips, instructions, and help
error messages. documentation are available and easy to understand.
US4: Ensure that all buttons, links, and interactive US9: Check if the system maintains consistency in layout,
elements are easily clickable and accessible. fonts, colors, and design elements.
US5: Validate that the system is responsive and US10: Test if the application supports accessibility
adapts well to different screen sizes and devices. features such as keyboard navigation and screen reader
compatibility.
Performance Testing Scenarios

TS1: Check how the system behaves under normal TS6: Check how the system handles login attempts.
user load conditions. TS7: Check if the system can process multiple
TS2: Check how the system handles a sudden spike transactions at the same time without delays.
in users (e.g., Black Friday sale). TS8: Check how the API responds when multiple requests
TS3: Check the maximum number of users the are sent at the same time.
system can handle before performance degrades. TS9: Check how the system performs under high load
TS4: Check if page load times increase as the (stress testing).
number of concurrent users grows. TS10: Verify how quickly the system recovers after a
TS5: Check the response time of the database under crash or failure (recovery testing).
heavy query load.
Security Testing Scenarios

SS1: Check if the system prevents unauthorized SS6: Verify if sensitive data (e.g., passwords, credit card
access to restricted areas. details) is encrypted in transit and at rest.
SS2: Verify that password policies (e.g., complexity, SS7: Ensure that multi-factor authentication (MFA) is
expiration, lockout after failed attempts) are implemented where required.
enforced. SS8: Check if the system prevents Cross-Site Request
SS3: Check if user sessions expire after a period of Forgery (CSRF) attacks.
inactivity. SS9: Verify that error messages do not expose sensitive
SS4: Test if the application is protected against SQL system information.
injection attacks. SS10: Check if the system properly logs and monitors
SS5: Check if the system is secure against Cross- security events for potential threats.
Site Scripting (XSS) attacks.
 Compatibility Testing Scenarios

CS1: Check if the application works correctly across CS6: Check if the system works correctly with different
different web browsers (e.g., Chrome, Firefox, Edge, hardware configurations (e.g., CPU, RAM, GPU variations).
Safari). CS7: Ensure that third-party integrations (e.g., payment
CS2: Verify that the system functions properly on gateways, APIs) work across different environments.
different operating systems (e.g., Windows, macOS, CS8: Test how the application behaves with different
Linux). versions of required software dependencies (e.g., Java, .NET,
CS3: Check if the application is responsive and works database versions).
on various screen sizes and resolutions. CS9: Check if file uploads and downloads work correctly
CS4: Ensure the system is compatible with different across various devices and operating systems.
mobile devices (e.g., Android, iOS). CS10: Verify that the system maintains compatibility with
CS5: Verify that the application supports different assistive technologies (e.g., screen readers, voice commands).
network conditions (e.g., 3G, 4G, 5G, Wi-Fi).
 Conclusion
 Mobile Application testing ensures a stable and high-quality app
 Adopting best practices improves user satisfaction and business success
Reference Page

https://www.browserstack.com/guide/mobile-app-testing-
1
best-practices

2 https://www.builder.ai/blog/app-testing

https://kobiton.com/blog/the-ultimate-guide-to-mobile-
3
testing
SOFTWARE TESTING
Thank You