
Learn how to test mobile applications for functionality, usability, compatibility, and performance across varied hardware, OS versions, and networks, ensuring native apps meet user experience expectations before release.
Understand three types of mobile applications—native, web, and hybrid—and how native apps access device features while web apps run in browsers and hybrids blend both.
Install and start the droid software on windows to view mobile devices, download the latest version, run the jar file, and prepare to view devices on the screen.
Navigate Jira dashboards to see tasks and bugs assigned to you, and update your profile, including password and profile image. Learn to reflect changes on your dashboard and manage projects.
Learn to report a new defect to Jira by logging in as tester, selecting category and subcategory, writing a clear description and steps to reproduce, and attaching screenshots.
Learn to search and filter issues in Jira by project, assignee, status, and type; search by text and priority to locate defects efficiently.
Outline the defect life cycle for a valid bug, from reporting and open status through assignment, fix, testing, and closing with evidence like screenshots.
Learn the defect life cycle from reporting to closure: testers log defects, assign to developers, handle rejections, reopen with client requirements and attachments, and validate fixes through builds and testing.
Discover how to design a standard test case format in Excel, with columns for ID, description, preconditions, steps, data, and expected results for robust mobile app testing.
Learn how to assign descriptive, readable test case IDs that clearly describe the testing scenario, such as login functionality with valid credentials, avoiding numeric-only IDs.
Learn to craft a test case description for login testing, focusing on admin users with valid credentials, using an Excel sheet to capture task details separate from the expected result.
Learn to define preconditions or prerequisites for a test case, including setup steps, dependencies, and conditions like browser, login, and cache clearance before execution.
Master test case steps for Android app testing by defining each step in serial order, one per line, from logon page to entering username and password to sign in.
Explore test data strategies for Android app login, using admin and guest credentials to drive different screens, and prepare task-specific data with fake or reference values.
Define expected results for every test step by matching client requirements, then verify messages such as login page open and the welcome message in each scenario.
Compare actual results with expected results during login steps, and use the status column to mark pass, blocked, or not executed.
Explore using the comments column after test execution to capture specific information, compare expected versus actual results, mark failures, and document login test outcomes.
Define a priority column for test cases using high, medium, and low levels. Use these priorities to guide execution under tight deadlines and focus on top priority tests.
Identify and categorize test cases by type, such as functional, compatibility, and usability, to prioritize, filter, and assign tasks for Android app manual testing.
Mobile application testing is a process by which developer developed for hand held mobile devices is tested for its functionality, usability and consistency.Mobile application testing can be automated or manual type of testing. Mobile applications either come pre-installed or can be installed from mobile software distribution platforms. Mobile devices have witnessed a phenomenal growth in the past few years. A study conducted by the Yankee Group predicts the generation of $4.2 billion in revenue by 2013 through 7 billion U.S. smartphone app downloads.
This Course going to cover following testing approaches
#1. Hardware testing:
The device including the internal processors, internal hardware, screen sizes, resolution, space or memory, camera, radio, Bluetooth, WIFI etc. This is sometimes referred to as, simple “Mobile Testing”.
#2. Software or Application testing:
The applications that work on mobile devices and their functionality is tested. It is called the “Mobile Application Testing” to differentiate it from the earlier method. Even in the mobile applications, there are few basic differences that are important to understand:
a) Native apps: A native application is created for use on a platform like mobile and tablets.
b) Mobile web apps are server-side apps to access website/s on mobile using different browsers like chrome, Firefox by connecting to a mobile network or wireless network like WIFI.
c) Hybrid apps are combinations of native app and web app. They run on devices or offline and are written using web technologies like HTML5 and CSS.