If you’re new to software testing, one of the first challenges you’ll face is understanding the terminology. From test cases to regression to smoke tests—there’s a whole vocabulary that helps QA professionals communicate clearly and effectively.
In this post, we’ll break down the essential testing terms you need to know to navigate the world of quality assurance with confidence.
✅ 1. Test Case
A test case is a set of steps, inputs, and expected results used to verify a specific feature or function.
Example:
Test Case: Verify login with valid credentials
Steps:
- Open login page
- Enter valid username and password
- Click “Login”
Expected Result: User is redirected to the dashboard
🧪 2. Test Plan
A test plan is a document that outlines the scope, approach, resources, and schedule of testing activities.
It answers:
- What will be tested?
- How will it be tested?
- Who will test it?
- What are the risks?
🔁 3. Regression Testing
Regression testing checks if new code changes have broken existing functionality.
Example:
You fix a bug in the login page. Regression testing makes sure the rest of the app still works as expected.
🚦 4. Smoke Testing
Smoke testing is a quick, high-level check to confirm that the basic functionality of an application works after a new build.
Think of it as:
“Does the app open? Can I log in? Can I click the main buttons?”
💥 5. Defect / Bug
A bug is an error, flaw, or unintended behavior in the software that causes it to produce incorrect or unexpected results.
Bug report example:
- Steps to reproduce
- Expected result
- Actual result
- Severity level
🧬 6. Functional Testing
Functional testing ensures that the system works according to the specified requirements.
Example:
Verifying that clicking “Add to Cart” correctly adds an item.
🧭 7. Exploratory Testing
Exploratory testing is an informal, unscripted process where testers actively explore the software to discover unexpected behavior or bugs.
It relies on the tester’s intuition, creativity, and product knowledge.
⚙️ 8. Automation Testing
Automation testing uses scripts or tools (like Selenium or Cypress) to run tests automatically, especially for repetitive or regression testing.
It saves time and increases efficiency over manual testing.
🧪 9. Unit Testing
Unit tests are written by developers to test individual pieces (units) of code, such as functions or methods, in isolation.
QA may not always write unit tests but should understand what they cover.
🌐 10. Integration Testing
Integration testing checks how different modules or services work together.
Example:
Does the payment system correctly connect with the order management system?
📋 11. Test Data
Test data refers to the input data used in test cases. This can include usernames, passwords, product names, or credit card numbers.
Good test data helps uncover hidden issues.
⏱️ 12. Test Execution
Test execution is the process of running test cases and logging the results—pass, fail, or blocked.
This step is usually done in a test management tool like qTest, Zephyr, or TestRail.
📉 13. Severity vs Priority
- Severity = How bad is the bug from a technical/user perspective?
- Priority = How soon should the bug be fixed?
Example:
A typo in a button label (low severity) might still need fixing before launch (high priority).
📊 14. Test Coverage
Test coverage refers to how much of the application is being tested—by test cases, automation, or exploratory testing.
High coverage = higher confidence in software quality.
🧠 15. UAT (User Acceptance Testing)
UAT is the final phase of testing where end users validate whether the software meets their needs before it goes live.
It’s often done by business users or clients.
🚀 Final Thoughts
Understanding testing vocabulary is essential for communicating clearly, writing better test cases, and collaborating effectively with your team.
Don’t worry if you don’t memorize them all at once—save this list, refer back often, and build your testing vocabulary over time.
