Manual Testing Glossary: Key Terms & Examples
Welcome to your essential guide for understanding the Manual Testing Glossary! This post is designed to help English learners and aspiring software testers grasp key terminology in the field. Mastering these terms is crucial for effective communication and success in Quality Assurance. We'll provide clear definitions, examples, and some vocabulary tips to help you avoid common language learning errors when discussing technical English topics. Our goal is to make these software testing terms accessible and easy to learn.
Table of Contents
What is Manual Testing Glossary?
This Manual Testing Glossary section breaks down fundamental vocabulary every manual tester should know. Understanding these core concepts will form the bedrock of your testing knowledge, helping you navigate the software development lifecycle (SDLC) with more confidence. We've compiled a list of essential software testing terms, their parts of speech, simple definitions, and practical examples to aid your learning.
Below is a table detailing key terms you'll encounter frequently. Pay attention to how these words are used in context; it's a great way to improve your technical English and grasp QA vocabulary.
| Vocabulary | Part of Speech | Simple Definition | Example Sentence(s) |
|---|---|---|---|
| Test Case | Noun | A set of conditions or variables under which a tester will determine if a system meets requirements. | The QA engineer wrote a detailed Test Case to verify the login functionality. |
| Test Plan | Noun | A document outlining the scope, approach, resources, and schedule of intended test activities. | The Test Plan clearly defined the objectives for the upcoming release. |
| Bug / Defect | Noun | An error, flaw, or fault in a computer program or system that causes it to produce an incorrect result. | A critical Bug was found during regression testing, preventing user registration. Learn more about software bugs. |
| Test Execution | Noun Phrase | The process of running test cases to check if the software behaves as expected. | Test Execution began as soon as the new build was deployed to the test environment. |
| Test Environment | Noun Phrase | The setup of software and hardware on which the testing team is to perform testing. | We need to ensure the Test Environment mirrors the production setup as closely as possible. |
| Test Data | Noun Phrase | Data specifically created or selected to be used in tests to verify system functionality. | Invalid Test Data was used to check how the system handles incorrect inputs. |
| Requirement | Noun | A condition or capability needed by a user to solve a problem or achieve an objective. | Each Requirement listed in the specification document must be covered by at least one test case. |
| Use Case | Noun | A description of how a user will perform tasks on your website or software application. | The Use Case for a new user registration involves several steps from form filling to email verification. |
| Traceability Matrix | Noun Phrase | A document that maps and traces user requirements with test cases. | The Traceability Matrix helps ensure that all requirements are tested. |
| Regression Testing | Noun Phrase | Testing existing software applications to make sure that a change or addition hasn't broken any existing functionality. | After the new feature was added, we performed Regression Testing on the entire module. |
| Smoke Testing | Noun Phrase | A preliminary type of software testing that checks if the most crucial functions of a program work. | A quick Smoke Testing was performed on the build to ensure it was stable enough for further testing. |
| Sanity Testing | Noun Phrase | A subset of regression testing, performed to ensure that code changes are working as expected. | After the bug fix, a Sanity Testing was conducted on the affected module. |
| User Acceptance Testing (UAT) | Noun Phrase | Testing performed by the end-user or client to verify/accept the software system before moving the software to production. | The client will conduct User Acceptance Testing (UAT) next week. |
| Test Script | Noun Phrase | A set of instructions that will be performed on the system under test to test that the system functions as expected. | Automated tests often follow a predefined Test Script. |
| Test Suite | Noun Phrase | A collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviours. | The Test Suite for login functionality includes test cases for valid, invalid, and forgotten password scenarios. |
More: Automation Testing Glossary Key Terms and Definitions
Common Phrases Used
Beyond individual words, manual testing involves specific phrases that convey common situations or outcomes. Learning these expressions will help you communicate more effectively with developers and other QA team members. This section on common phrases provides practical usage explanations, which are vital vocabulary tips for anyone looking to master manual test definitions and avoid language learning errors in a professional setting.
Here are some useful expressions, their meanings, and examples of how they are used in daily testing activities:
| Phrase | Usage Explanation | Example Sentence(s) |
|---|---|---|
| Cannot Reproduce (CNR) | Used when a tester is unable to make a reported bug happen again. | The developer marked the defect as Cannot Reproduce (CNR) after several attempts on their machine. |
| As Per Design (APD) / Works As Designed (WAD) | Used when the software is behaving according to the documented design or specifications, even if it seems like an issue. | The reported issue with the button color was closed as Works As Designed (WAD), as it matched the style guide. |
| Out of Scope | Refers to features or functionalities that are not meant to be tested in the current testing cycle or project. | Testing the admin panel is currently Out of Scope for this sprint, as per the test plan. |
| Test Coverage | Refers to the extent to which the testing activities have covered the application's functionality. | We aim for 95% Test Coverage for all critical features before the release. |
| Pass / Fail Criteria | The rules or conditions that determine whether a test case has passed or failed. | The Pass / Fail Criteria for this test case state that the user must receive a confirmation email within 5 seconds. |
| Raise a Defect / Log a Bug | The act of formally reporting an issue found during testing in a bug tracking system. | If the application crashes, you need to Raise a Defect with detailed steps to reproduce it. |
| End-to-End Testing | A testing methodology to test the application flow from start to end. | We are conducting End-to-End Testing to ensure the entire user journey from registration to purchase is seamless. For more on software testing methodologies, see resources like ISTQB (International Software Testing Qualifications Board). |
More: Software Testing Glossary: Essential QA Terms
Conclusion
Mastering the vocabulary within this Manual Testing Glossary is a significant step in your journey to becoming proficient in software testing. Understanding these software testing terms and common phrases will not only boost your confidence but also improve your ability to communicate clearly and effectively within a QA team. Keep practicing, use these terms in context, and don't be afraid to ask questions. Consistent learning and application are key to overcoming any language learning errors and truly understanding technical English. Good luck with your studies!