Manual testing is the process of verifying and validating the software to ensure that the software meets the requirements. Tester play the role of an end user whereby they utilize most of the application’s features to ensure correct behavior.
Types of Manual Testing
Functional Testing:
In functional testing, we are verifying and validating all the functionalities of an application. By performing functional testing, we can ensure that the application performs correctly and covers all the functionalities based on the Requirement documents.Quite simply, functional testing looks at what software is supposed to do and makes sure it actually does that.
We are performing functional testing through Manual resources and also with Automated scripts.
Usability Testing:
The purpose of usability testing is to ensure that the application is user-friendly. To ensure the application is user friendly, we are performing the usability testing from the end-users’ perspective. We are considering the following points during the usability testing:
We are performing usability testing through Manual resources and also with Automated scripts.
GUI Testing:
Through GUI testing we are ensuring all the UI elements in the application are perfectly displayed and placed. We are performing GUI testing through Manual resources and also with Automated scripts (other than image content).
Compatibility Testing:
The purpose of Compatibility Testing is to ensure that the application works as expected in different environments, operating systems, browsers and mobile devices. We are performing compatibility testing to ensure the following:
We are performing usability testing through Manual resources and also with Automated scripts.
Integration Testing:
We are performing Integration testing to ensure that the application works as expected after integrating separate modules or units in to one group. We are performing integration testing using the following approaches:
Bottom up approach:
The Integration testing starts from the lowest module and gradually progresses towards the upper modules of the application. This integration continues till all the modules are integrated and the entire application is tested as a single unit.
Top down approach:
In this approach, testing starts from the top most module and gradually progress towards the lower modules. Only the top module is unit tested in isolation. After this, the lower modules are integrated one by one. The process is repeated until all the modules are integrated and tested.
We are performing usability testing through Manual resources and also with Automated scripts.
Regression Testing:
The purpose of regression testing is to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. We used to perform regression testing after bug fixes or an enhancement in the application. Since regression testing is typically done after every deployment, it is easy enough to automate all regression tests, so we used to perform the regression testing through automated scripts.
End-To-End Testing:
End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish and to ensure that the integrated components of an application function as expected. During end-to-end testing, the entire application will be tested. We used to perform end-to-end testing before every release of the application to the customer.
We are performing end-to-end testing through Manual resources and also with Automated scripts.