Certification: AI-driven Test Automation

QA Terminology

QA Terminology

Below are the most commonly used QA terminologies that every QA professional ought to know. Make sure you’re familiar with all of them:

  1. Test Case: A set of conditions or actions used to determine if a system behaves as expected.
  2. Bug/Defect: A problem or error in a software program.
  3. Smoke Testing: Basic tests to check if a new software version is stable enough for more in-depth testing.
  4. Regression Testing: Verifying if previously working functionality still works after new changes.
  5. Unit Testing: Testing the smallest part of an application in isolation (e.g., functions or methods). This testing is commonly done by developers.
  6. Integration Testing: Testing interactions between integrated components or systems.
  7. System Testing: Testing the complete system to ensure it meets the requirements.
  8. UAT (User Acceptance Testing): The final testing phase where actual users try the software to make sure it works in real-life scenarios.
  9. Test Suite: A collection of test cases related to a specific functionality.
  10. Sanity Testing: Quick checks after a bug has been fixed to ensure the specific fix works.
  11. Black Box Testing: Testing software based on output, without knowing its internal workings. For example, when an end-user interacts with the website’s UI without having access to the code.
  12. White Box Testing: Testing software with knowledge of its internal workings.
  13. Test Plan: A detailed document outlining the testing strategy, objectives, resources, schedule, and deliverables.
  14. Test Script: Step-by-step instructions for a particular test.
  15. Test Scenario: A high-level idea of what to test. It can have multiple test cases.
  16. Exploratory Testing: Testing the software without a set plan, exploring and learning the application.
  17. Boundary Testing: Testing the limits (edges or boundaries) of the software input.
  18. Functional Testing: Testing software functions by feeding them input and examining the output.
  19. Non-functional Testing: Testing non-operational aspects of a software, like performance, usability, or security.
  20. Test Environment: A controlled setting where testing is conducted.

If you stumble upon a term that is not mentioned above, you can likely find the explanation here.

Test your knowledge

Black Box Testing
Exploratory Testing
Sanity Testing
Boundary Testing

Functional Testing
White Box Testing
System Testing
Non-functional Testing