Introduction: Why Terminology Matters
Imagine you’re preparing for a QA interview and the interviewer starts using words like defect, test case, regression testing, and severity. If you don’t understand these clearly, it can feel confusing and stressful.
This is very common for beginners in software testing. Learning manual testing terminologies is one of the first steps in becoming confident in QA. These terms are used daily in real software projects across the USA, and interviewers often ask about them to check your basic understanding.
Important Manual Testing Terms Explained
Below are the most important software testing terminology concepts every beginner should know. Think of this as your manual testing glossary.
The Basics
- Software Testing: Checking whether an application works correctly against requirements.
- Manual Testing: Testing software by hand without using automation scripts or tools.
- Build: A specific version of the software provided by developers for testing.
- Release: The final version of software delivered to the actual users/production.
Planning & Documentation
- Test Scenario: A high-level description of what to test (e.g., "Check Login functionality").
- Test Case: A detailed step-by-step instruction on how to test a feature, including expected results.
- Test Plan: A document describing the scope, approach, resources, and schedule of testing activities.
- Requirements Traceability Matrix (RTM): A document that maps requirements to their corresponding test cases to ensure full coverage.
Defects & Issues
- Defect / Bug: Any mismatch between the actual behavior and the expected behavior of the software.
- Severity: The technical impact of a bug on the system (e.g., a system crash has High Severity).
- Priority: The business urgency to fix a bug (e.g., a typo on the homepage might be High Priority).
- Defect Life Cycle: The specific stages a bug moves through (New -> Open -> Fixed -> Retest -> Closed).
Types of Testing Execution
- Smoke Testing: Preliminary testing to verify that the most critical functions of a build work correctly.
- Sanity Testing: Brief testing to verify that a specific bug fix or code change works as expected.
- Regression Testing: Re-testing existing features to ensure new code changes haven't broken old functionality.
- Retesting: Testing a specific bug again after the developer claims it has been fixed.
- UAT (User Acceptance Testing): The final phase where actual users test the software to see if it meets their business needs.
QA Terms Commonly Asked in Interviews
Interviewers love to ask for comparisons. Here are the most frequent ones:
- Severity vs Priority: Severity is about the technical impact; Priority is about the business timeline.
- Verification vs Validation: Verification is checking documents (Static); Validation is testing the running software (Dynamic).
- Test Case vs Test Scenario: Scenario is "What" to test; Case is "How" to test it.
How These Terms Connect in Real Projects
Let’s see how these terminologies come together in a typical day at a USA-based software company:
The project starts with Requirement Analysis. QA then creates Test Scenarios and Test Cases. Once the developers provide a Build in the Test Environment, QA performs Smoke Testing. If it passes, the full Execution begins.
When a Defect is found, it is reported with a specific Severity. After the developer fixes it, QA performs Retesting followed by Regression Testing to ensure the rest of the app is stable. Finally, after UAT, the software is ready for Release.
Frequently Asked Questions
Is it hard to remember all these terms? Not at all! As you start writing test cases and reporting bugs, these terms will become part of your everyday vocabulary.
Do I need to know automation terms for a manual testing interview? It helps, but for a Manual QA role, mastering these fundamental terms is much more important.
What is the difference between a bug and a defect? In common industry usage, they are often used interchangeably. Technically, a "Bug" is found by programmers, while a "Defect" is found by testers.
Key Takeaways
- ✓ Terminologies are the "language" of QA.
- ✓ Understanding these terms makes you sound professional in interviews.
- ✓ Focus on the differences (Retesting vs Regression, etc.) as these are common traps.
Want to see these terms in action? Check out our guide on How to Write a Professional Bug Report to see how Severity and Priority are used in real life!