Overview of Manual Testing and finding bugs

What is manual testing?

Manual testing is the process of testing software without the use of automation tools. It requires a tester to act as an end user, interacting with the application to identify any bugs or issues.

How to find the bugs in manual testing?

There are procedures for identifying bugs during manual testing:

1. Understanding Requirements and Specifications of the Apps: Carefully examine the app release documentation, requirements, and specifications to pinpoint the areas where the bug has occurred, particularly in relation to new features.
2. Create Test Cases: Create the test cases and make sure to include both the actual and expected results.
3. Explore Different types of testing: Complete the following steps: Functional Testing, UI/UX Testing, Boundary Testing, Integration Testing, and Performance Testing.
4. Follow the process: Adopt a structured method for testing and outline the steps for the test cases. Manually execute the test cases by interacting with the application, then compare the actual outcomes with the expected results.
5. Use Exploratory Testing: Conduct exploratory testing to identify bugs in areas not addressed by test cases by inputting invalid data into the application.
6. Pay attention to details: Keep an eye out for any unusual app behavior, including crashes, slow performance, and error messages like a 404 error. Also, check for misalignments, UI bugs, spelling and grammar mistakes, incorrect data in forms, or improper error handling.
7. Test across different environments: Conduct tests on various browsers including Chrome, Mozilla, Opera, and Edge, as well as on operating systems like Microsoft Windows, Ubuntu, and MacOS. Test applications on different devices such as Android and iOS. Additionally, evaluate the applications in multiple environments like DEV, TEST, and UAT to identify any environment-specific bugs.
8. Use debugging tools: Press F12 in Chrome, Opera and Mozilla to access the browser developer tools, where you can investigate bugs and monitor network requests, console errors, and other browser diagnostics.
9. Communicate with developers: Document any issues encountered in the environment by capturing screenshots, compiling a list of bugs, and outlining test cases. Coordinate with developers to confirm whether a bug exists.
10. Retest and Regression testing: Conduct a retest or perform regression testing to confirm that the bugs have been fixed and resolved.