Introduction: Your First Day as a QA
Picture this: you just landed your first job as a QA in the US. Your boss tells you to "follow the manual testing process" on your first day. You know the basics of testing, but you're curious about what the actual procedure is like at work.
This is a common mistake that new people make. A lot of people know about testing principles, but they don't really know how testing works step by step in real software projects. Companies have a set way of testing software so that teams can do it the same way every time and not make mistakes.
The good news is that it's not hard to comprehend how to do manual testing. Testing becomes more systematic and predictable after you know the steps.
What is the process for manual testing?
Following certain stages is how the manual testing method tests software in an organized way. It helps QA teams test apps properly and in the same way every time. In manual testing, this step is part of the Software Testing Life Cycle (STLC).
Testers don't just verify features at random; they follow a precise process:
- Understand requirements
- Write test cases
- Execute tests
- Report bugs
- Verify fixes
A Step-by-Step Guide to Manual Testing
Now let's go over all the steps of manual testing that are employed in real projects.
Step 1: Requirement Analysis
This is the first thing you do. Testers read the requirements documents to find out what the software needs to do. They figure out what needs to be tested and talk to developers or product managers to clear up any questions.
Step 2: Test Planning
In this step, the plan for testing is made. The Test Lead or QA Manager makes the call on what to check, the scope of testing, the schedule, and team duties.
Step 3: Test Case Design
Testers now construct test cases based on what is needed. A test case includes steps to take, data for testing, and the expected outcome. Writing both good and bad scenarios is a common daily task for novices.
Step 4: Test Environment Setup
The environment must be ready before testing can begin. This includes putting the app on your computer, creating test accounts, and getting test data ready.
Step 5: Test Execution
This is where the real testing takes place. Testers run test cases and check to see if the expected result matches the actual result. You mark it as Pass if results match and Fail if they are different.
Step 6: Defect Reporting
Testers use platforms like Jira to report bugs. A defect report normally has steps to reproduce the bug, screenshots, and priority levels.
Step 7: Retesting & Regression Testing
Testers check the bugs again after developers address them (Retesting). They also look at other features to make sure nothing else is broken (Regression Testing).
Step 8: Test Closure
QA teams write a summary report containing test results, bugs discovered, and overall quality level. This is the final stage of the manual testing process.
Example: Manual Testing for an E-commerce Website
Let's look at a real-world example for an "Add to Cart" feature:
- Requirement analysis: Figure out how the cart should work.
- Design test cases: Write cases for adding, removing, and changing quantities.
- Test execution: Run the tests on the website.
- Reporting defects: Find a bug where the cart shows the wrong total price.
- Retesting: Checking the price calculation again after the developer fix.
- Test closure: Final sign-off that the feature is ready.
Why It's Important to Follow a Testing Process
Following a disciplined QA testing approach helps find bugs early and saves the firm money. Structured testing workflows are critical for software companies in the US since their apps need to work for thousands or millions of users. Without a methodology, important bugs can easily be missed.
Mistakes That Newbies Make
- Not doing requirement analysis properly.
- Making test scenarios that are vague or unclear.
- Not paying attention to "edge cases" (unusual user actions).
- Reporting bugs with incomplete information.
Frequently Asked Questions
What is the first thing you do in manual testing?
The first step is Requirement Analysis. You must understand what needs to be tested before writing cases.
Is manual testing hard?
No. If you follow these 8 steps and practice, the process becomes very easy.
Do I need to know how to code?
No, manual testing focuses on how software works from a user perspective, not programming.
What tools are common?
Jira, Excel, Azure DevOps, and TestRail are the most used tools in the US.
Key Takeaways
- Follow the STLC for a systematic approach.
- Clear documentation (Test Cases/Bug Reports) is essential.
- Regression testing ensures stability after changes.
Ready to practice? Start by picking a website you use daily and try to write down the requirement analysis for its login feature!