ISTQB Foundation Level Certification Syllabus 

ISTQB Foundation Level Certification Syllabus  IntroductionInternational Software Testing Qualifications Board(ISTQB) is a globally recognised organisation which conducts certification courses and exams for software testers. ISTQB...
HomeTechnology NewsThe Steps Involved in the Manual Testing Process

The Steps Involved in the Manual Testing Process

The Steps Involved in the Manual Testing Process

Manual testing is performed by individuals following a set of logical steps. The initial phase in the manual testing process is to become familiar with both the ordering company and the end user’s expectations of the product, and the final step is product release.

The whole process takes time, but it is the human factor that allows this type of testing to be successful in creating a great product. Manual testing is easier to execute than automation because it requires fewer technical knowledge and there are no automation tools to learn or set up. However, testers must be familiar with various manual testing approaches and test management software. The primary goal of manual testing, as with all methods of software testing, is to compare the system to the established requirements or user stories to detect faults, then assess the programme and support the development team in generating defect-free software.

Manual Testing Steps

All forms of software testing are classified as either manual or automated. While the testing stages for manual and automation testing are quite similar, the following phases are specific to the manual testing method.

  1. Gathering Requirements

Understanding the application to be tested and what the end-user should expect from the product is the first step in the testing process. This is accomplished by assessing all accessible papers, researching current systems and integrations, and communicating with stakeholders to better understand their business requirements.


The information gathered from this study will influence the testing strategy and testing implementation plan, thus having access to additional resources, such as chats with developers while they run a demo of the product ahead of testing, can be quite beneficial. Working closely with development and QA can be advantageous since daily integration allows each discipline to have a more natural understanding of how the other side operates.

  1. Discussion and sharing

After gathering and adopting various info on the programme to be tested, the following step is to consolidate and prioritise the information into useful components ready for use in constructing test cases and test scenarios. The kind of testing to be performed, as well as the scope of testing and the time available, must all be taken into account. The goal at this phase is for QA to thoroughly understand the product, therefore sharing and debating the current state of play with various stakeholders might help to uncover previously unknown sources of data or interesting areas of study.


Having a visual overview of the software testing project that highlights the full scope and details of the situation can make understanding much easier for all parties involved. Mind maps are increasingly being utilised in business and software testing to create simple route maps and reminders. When attempting to deal with everyday overwhelm, a frequent suggestion is to write it all down.Mind maps are a more systematic manner of achieving this. Mind maps can be useful for team leaders to share an overview with the team, who can also routinely update their testing status there as the project advances. Mind maps should not be used in place of proper test documentation and progress updates, but rather as a lightweight notebook to aid with test planning and accountability.


  1. Configuration of the Test Environment and Resources

Because manual testing resembles the end-user experience, testing in a specialised and filled testing environment standardised the product’s performance in the lab. It facilitates the detection of bugs for correction before the product is issued.


The test environment may be prepared once the requirements are established and a basic structure for how to proceed is in place. By planning ahead of time, enough time can be allocated to acquire and set up manual testing tools, hardware, and other related materials and assets required for the test runs. Planning also entails naming people who must be involved, ensuring they have been notified, and scheduling the appropriate time.

  1. Development of Test Scenarios and Test Cases


Following the study of requirements and user stories, it will be evident what and how to test. Documentation is required for projects that conform to process, which usually includes writing test cases. When testing begins and materials are provided with the team, testers thoroughly analyse the specification documents, collect in-depth knowledge about the scope of testing, and then develop high-level test scenarios and detailed level test cases. Test cases provide instructions on how and what to test, what data to utilise, and what results to expect.

  1. Execution of Tests and Reporting of Defects


Test execution is the most important task in software testing. Each test case in manual testing is carried out by one or more people who act in keeping with the instructions outlined in the test cases. The tester’s primary goal is to achieve the stated goal while recording any differences between the expected and actual. Anything discovered that does not meet the requirements will be documented as a bug in the report and forwarded to the developers, with the test case status for this item set to fail.

  1. Retesting and Closure of Defects


A defect will be assigned to each failed test. The goal of testing is not only to find and report faults, but also to assure that all reported issues have been acknowledged, solved, and retested for confirmation. Once the developers have returned a resolved issue, it is the job of the tester to retest the reported defect to confirm the fix so that the ticket can be officially closed. Because testers are responsible for confirming any fixes, it is the tester’s obligation to update the status of the test cases whenever a returned defect has been proved to be resolved. All test cases must be marked as passed before a test team can sign off on the product under test.


  1. Comments and Suggestions

Before a system is released, it is tested so that all parties may learn about the overall quality of the product. The manual testing process is completed with the distribution of a test report to all stakeholders. Before testing can be signed off on, the results are subjected to a feedback and recommendations process, which begins with testers self-checking their work for flaws. It is therefore recommended that each tester submit their work for peer and team leader assessment before consolidating the results into a test summary document. If necessary, the team may give recommendations on areas for improvement at this time.


The test report should include all information regarding the product’s testing status, as well as different testing metrics, a list of the areas tested, a statement of any places out of scope, and non-testable things. The test report is then sent to the Business Analyst (BA), who may offer input and make recommendations for how the testing or product could be improved based on their understanding of the product from the customer’s perspective.


  1. Product Release, Test Cases, and Database Upkeep

Once it has been shown that the product meets the needs of the business owner, it can be delivered to a release manager and scheduled for release. Although the product has now passed QA, it may be returned if something goes wrong once it hits the market, or if any changes have been made to the product since review.


  1. Keeping test cases up to date


In preparation for a future round of regression testing, it is a good idea to update and keep the test cases on file in case the need arises. This includes using excellent version control to ensure that no old test cases are performed by mistake or a previously logged bug is reintroduced.


Conclusion : 

Finally, the manual testing procedure is critical for assuring the quality and dependability of software programmes. Testing teams can find problems, improve user experiences, and ultimately contribute to the success of software projects by following these procedures carefully. When performed with care and attention to detail, manual testing plays a crucial role in delivering reliable and error-free software solutions to end users.


Learn the step-by-step process of manual testing with our manual testing full course designed for beginners. Discover how manual and automated testing can work together in an effective testing strategy. Check out the GrotechMinds Manual Testing course to master the art of manual testing to ensure software quality.