Chapter 05

Manual testing

What is manual testing

Manual testing is the process of manually testing software for defects by executing test cases without the use of automation tools. This type of testing is typically done by a human tester and is used to validate the functionality of the software, ensure it meets the specified requirements, and identify any bugs or issues. It can include testing the software's user interface, functional and non-functional requirements, and overall performance. The goal of manual testing is to identify any issues or defects in the software before it is released to end-users.

How to do manual testing

Manual testing involves several steps to ensure that software is thoroughly tested and any defects are identified. The steps include:

• Reviewing the requirements: The tester reviews the requirements document to understand the functionality of the software and the expected results.

• Creating test cases: The tester creates a set of test cases based on the requirements. Each test case includes a set of inputs and expected outputs.

• Executing test cases: The tester executes the test cases manually by inputting the test data and observing the software's output. The tester compares the output to the expected results to identify any defects.

• Documenting defects: If a defect is found, the tester documents it by creating a bug report. The report includes a detailed description of the defect and steps to reproduce it.

• Retesting: After the defects are fixed, the tester retests the software to ensure that the defects have been resolved.

• Reporting: The tester creates a final report that includes the status of the testing, the number of defects found, and the overall quality of the software.

It's important to note that manual testing is not a one-time process, it needs to be done multiple times before release and even after release to ensure software quality.

What are the manual testing tools

Manual testing tools are software applications or platforms that aid manual testers in creating, executing, and managing test cases. These tools are used to streamline the testing process and improve the efficiency and effectiveness of manual testing. Some examples of manual testing tools include:

• Test Case Management Tools: These tools are used to create, manage, and organize test cases. They also provide a way to track the status of test cases and defects. Examples include TestRail, Zephyr, and TestLink.

• Test Execution Tools: These tools are used to execute test cases and record the results. They also provide a way to track the progress of testing and identify defects. Examples include TestLink, TestRail, and qTest.

• Defect Tracking Tools: These tools are used to track and manage defects found during testing. They provide a way to assign defects to developers, track their status, and report on the number of defects found. Examples include Jira, Bugzilla, and Mantis.

• Test Management and Reporting Tools: These tools are used to manage and report on the overall testing process. They provide a way to track the progress of testing, generate test reports, and analyze test results. Examples include HP Quality Center and Test Collab.

• Mind Mapping Tools: These tools are used to create visual representation of ideas, process, and test case scenarios. Examples include XMind and MindNode

It's important to note that while these tools can aid in manual testing, they can't replace human testers. They are just a tool to improve efficiency, productivity, and organization.

What are the best practices for writing test cases.

Writing test cases is a crucial step in the manual testing process, as it helps ensure that software is thoroughly tested and any defects are identified. Here are some best practices for writing test cases:

• Clearly define the test objective: Each test case should have a clear and specific objective, such as testing a specific feature or functionality.

• Use a consistent format: Test cases should be written in a consistent format, including a unique ID, a title, a description of the test, the steps to execute the test, and the expected results.

• Be detailed: Test cases should be detailed enough to provide clear instructions on how to execute the test and what to look for in the results.

• Prioritize test cases: Test cases should be prioritized based on their importance, so that the most critical tests are executed first.

• Use clear and simple language: Test cases should be written in clear and simple language, so that they are easy to understand and execute.

• Include test data: Test cases should include the test data needed to execute the test.

By following these best practices, you can help ensure that test cases are effective in identifying defects and improving the overall quality of the software.