Manual Testing, Manual Testing on Mobile Application
What is Manual Testing?
Manual testing is a software testing process where test cases are executed manually using an automated tool. Test case reports are created manually. [1] Manual software testing is the most primitive technique among all types of testing and helps manage critical bugs in the software. [2]
Test Methods Used in Manual Testing
White box: It is a type of test in which the internal structure, design, and explanation of the content are tested. It tests whether the designed back-end system program is working properly.
Black box testing: It is a test performed without knowing the internal structure of the code or system. Tests through the application user interface, focusing on test components, inputs, outputs, and expected behaviors.
Software Testing Levels Used in Manual Testing
Unit testing: This is done to ensure that smaller units of code of the software run as expected to ensure the correctness of the source.
System testing: Testing the system as a whole. It provides a smooth and satisfactory user experience by testing whether the system meets its conditions.
Integration testing: This is done to reveal and control errors during the integration of different software and to operate the system as a whole.
Acceptance test: It is a user-based test to ensure that the calculations comply with the acceptance criteria according to the user's needs and requirements. [4]
Mobile Application Testing
Mobile app testing recognizes that it is possible to resolve a process, and test devices and security across a variety of mobile devices, operating systems, and network environments.
The goal is to provide a high-quality, error-free user experience and be able to meet the target and standards developed before release. [5]
Mobile Application Types
Mobile application types are divided into 3: Native Applications, Web Applications, and Hybrid Applications.
Native apps: Native mobile apps are built specifically for a particular operating system. They are called "native" because they are specific to a particular device or platform. Twitter, WhatsApp, Facebook, Instagram, and Skype. These applications have been specially developed for the target platform to work quickly and smoothly on users' mobile devices. [6]
Web applications: Web applications refer to websites that can create native app-like experiences on mobile devices. These applications are available on computers and mobile phones and are compatible with multiple operating systems. These applications are general.
• Web-based games
• On websites and applications linked to them
• On e-commerce sites
was used.
Hybrid applications: Hybrid applications are created by combining native and web applications. Like native applications, it can be included in the App Store and all the features of the device can be used. Uber and Amazon Appstore are examples of these applications. [7]
Manual Testing Processes in Mobile Applications
Manual testing in mobile apps focuses on examining all systems and features in a product to see if they work as the customer expects. So what should our process be like?
1) Plan: It is the first step of the testing process, covering the goals and criteria of the test.
2) Testing on Real Devices, and Emulators: While emulators provide a controlled environment for the initial testing stages, real devices test the application performance in real use cases. This dual approach allows the application to be tested for compatibility on different hardware, operating systems, and network environments.
3) Choose Complex Use Cases: It exposes the application to work in challenging situations. It should represent real-world situations the user might encounter, such as handling interruptions and testing the application when those interruptions could be incoming calls or notifications.
4) Better Click Paths: It refers to the order and number of steps the user takes to perform a function within the application. Evaluating these paths in manual testing ensures that users can easily navigate the application.[5]
How Do We Test Mobile Applications with Manual Testing?
Mobile applications need to be tested manually using both real device clouds and emulators/simulators.
We can test our application against today’s trends with Real Device Cloud, emulators, and simulators.
Testing on Real Device Cloud:
Testing Using Real Devices: The application needs to be tested on a variety of mobile devices with different operating systems and features.
Real-World Testing: The application needs to be experienced and tested as users experience it, with device-specific situations such as camera, GPS, and battery usage.
Network Conditions: It is necessary to test the application on various network types and speeds such as 3G, 4G, and Wi-Fi.
Gesture and Interactivity: It is necessary to test the app's responsiveness to touch gestures, screen rotations, and other physical actions.
Emulators and Simulators
Early Error Detection: This is done to save time by detecting and fixing errors early in the development phase.
Parallel Testing: Allows simultaneous operation and testing of multiple devices for different versions and screen resolutions.
Environment: Tests different environments and conditions, such as low battery, intermittent connections, or incoming calls.
Current fashion
Transition to Cloud-Based Testing: With today's trends, the use of cloud-based real-device testing has also increased. It is a type of testing that uses cloud-based tools to mimic real-world user traffic and environments to test all types of applications, networks, and infrastructure.
User Engagement Metrics: Ensuring a smooth app experience through comprehensive and detailed testing will make the app more efficient for users. All of these need to be tested. [5]
For example, let's test the mobile application of a shopping site.
Let's think about and test the mobile application of a shopping site. Let's assume that our application is downloaded to our phone and we subscribe.
First, we need to click on our mobile application.
After clicking, it should direct us to the login screen. Then, what login options does the mobile application offer us, for example, our phone number, e-mail address, registered Google account, etc? We will enter this and determine it.
If I want to log in with a phone number, the number entry screen should appear. If I log in with an email address, the box to enter the email address should appear. If I log in with a Google account, it should direct me to the screen where the necessary parameters will be entered. We are testing these.
Let's take the option to log in with an email address and select it. It directed me to the relevant screen. I entered my username, that is, my e-mail address, and clicked the log in button. The password screen came up, I entered my password and logged in.
After logging in, you will enter the home page. All icons on the homepage must be working. For example, when I click on the categories section, the products in the category I have selected should be listed. When I filter, the products should be listed according to the features I have selected.
Okay, let me test the payment section, I add the product to my cart, and click on my cart. After entering the My Cart screen, I click on the complete shopping button.
It should direct me to the page with my address information and payment options. In this section, I choose my address information and payment method. Of course, my address information registered here must also be correct.
After selecting the payment method, I chose to pay by card and it should redirect me to the screen where the card information is entered. After entering my information, I completed the payment and ordered the product successfully. I carried out all these operations and tested whether the system was working correctly. I tested a few cases this way and made a short example.
TestRail
TestRail is a web-based test management tool developed by Gurock software that generally helps administrators track the progress of tests and allows test engineers to create test cases in an organized and fast manner. It supports different Windows operating systems such as Windows XP and Vista 7.
TestRail allows us to create projects, write test scenarios, run the scenarios we wrote in a certain order, find errors, and report the errors we find. We can divide test cases into sections. This allows us to easily find test cases when we test a section. Every scenario that runs has a status. We can get reports based on % value with options such as Failed, and Successful. TestRail can be integrated with other tools — JIRA, Bugzilla, Fogbugz, Version One, TFS, GitHub, etc. When we enter the site, the titles OVERVIEW, THINGS TO BE DONE, MILESTONES, TEST STUDIES & RESULTS, TEST CASES, and REPORTS appear on the main screen. [8]
Overview
Contains a chart showing the test execution status in a project. We can view test scenarios, runs, and reports of the project.
To do
Displays the user's to-do list and test conditions that the user must perform.
Milestones
It helps determine the list of requirements tested in the sprint. Separate milestones are created for each iteration.
Test Runs and Results
Here we determine which test scenarios we will run. To do this, we can select the test scenarios to be run from above and add them to the list. We run the test scenarios we choose. We can determine whether the scenarios we run are successful or unsuccessful.
Test Cases
When we click on this section, there are title, section, template, priority, references, prerequisites, and steps-expected result sections. We need to fill out these sections in accordance with the requirements of our project. In this way, we can achieve a more understandable project testing process.
Reports
The results of each test case run appear here. We can see the status of the entire project. [9]
References
[1] https://www.linkedin.com/pulse/manual-testing-tutorial-what-types-concepts-mamta-sharma
[2] https://testeryou.com/tr/dijital-bir-dunyada-manuel-test/
[3]https://prometteursolutions.com/blog/wpcontent/uploads/2021/02/under6.png
[4]https://miro.medium.com/v2/resize:fit:1129/1*iPJsEBetiuTdZKhZDqCOuQ.jpeg
[5] https://testsigma.com/blog/how-to-test-mobile-application-manually/
[6] https://www.niobehosting.com/blog/native-mobil-uygulama/
[7] https://appmaster.io/tr/blog/yazilim-testi-turleri#sistem-testi
[8] https://serdartorun.blogspot.com/2017/02/testrail-incelemesi.html
[9] https://furkan-akbas.medium.com/testrail-nedir-nas%C4%B1l-kullan%C4%B1l%C4%B1r-a950cd9a94aa
