Beginner Glossary · Automation Testing
Automation Testing Glossary for Beginners
Quick summary — automation testing glossary
Essential terms every automation tester should know. This glossary covers the concepts, tools, and practices that form the foundation of automation testing.
In this glossary you will learn:
- Core concepts — test, assertion, locator, wait.
- Tools — Selenium, Playwright, Postman.
- Frameworks — TestNG, Pytest, POM, BDD.
- CI/CD — pipelines, runs, reports.
- Best practices — how to build reliable tests.
SECTION 01Core concepts
These are the foundational terms you need to understand before you start writing your first test.
| Term | Meaning | Example |
|---|---|---|
| Test | A script that verifies a specific behaviour | A test that checks login works |
| Assertion | A check that the actual result matches the expected result | assert title == "Dashboard" |
| Locator | A way to find an element on the page | By.id("username") |
| Wait | Pausing test execution until a condition is met | Wait for element to be visible |
| Test Suite | A collection of related tests | All login tests |
| Test Case | A single scenario tested | "Valid login" |
SECTION 02Tools
These are the most common tools in automation testing.
| Tool | What It Does | Common Use |
|---|---|---|
| Selenium | Browser automation | Web UI testing |
| Playwright | Browser automation (modern) | Web UI testing (faster) |
| Cypress | Browser automation (JS) | Frontend testing |
| Postman | API testing | Test REST APIs |
| JMeter | Performance testing | Load and stress tests |
| Appium | Mobile automation | iOS / Android testing |
SECTION 03Frameworks
Frameworks provide structure for your tests. Here are the essential terms.
| Term | Meaning | Example |
|---|---|---|
| TestNG | Testing framework for Java | Test configuration, parallel runs |
| Pytest | Testing framework for Python | Fixtures, parametrize |
| POM | Page Object Model — design pattern | Separate page logic from tests |
| BDD | Behaviour-Driven Development | Cucumber with Given/When/Then |
| Data-Driven | Tests that use external data | Login tests with 20 users |
| Keyword-Driven | Tests driven by keywords | "click", "type", "verify" |
SECTION 04CI/CD terms
Automation tests are most valuable when integrated into CI/CD pipelines. Here are the terms.
| Term | Meaning | Example |
|---|---|---|
| CI | Continuous Integration | Tests run on every push |
| CD | Continuous Delivery / Deployment | Automated release process |
| Pipeline | Automated sequence of steps | Build → test → deploy |
| Build | A single run of the pipeline | Build #42 |
| Artifact | Output of a build | Test reports, binaries |
| Flaky Test | A test that sometimes fails without code changes | Intermittent failures |
SECTION 05Best practices
These are the terms and practices that separate good automation from fragile automation.
| Term | Meaning |
|---|---|
| Page Object | A class that represents a page and its elements |
| Test Data | Inputs for tests — separate from test logic |
| Test Environment | Where tests run (dev, staging, prod) |
| Smoke Test | Quick tests to verify basic functionality |
| Regression Test | Tests to ensure nothing broke |
| Test Coverage | The percentage of code tested |
SECTION 06Interview Q&A — glossary terms
Q1What is an assertion?
An assertion is a check that the actual result matches the expected result. If they do not match, the test fails.
Q2What is a locator?
A locator is a way to find an element on a page — by ID, class, XPath, CSS selector, or accessibility attributes.
Q3What is the Page Object Model?
POM is a design pattern where each page is represented by a class that contains its elements and actions. This separates page logic from test logic.
Q4What is a flaky test?
A flaky test is a test that sometimes fails without any code changes. Flaky tests are usually caused by timing issues, environment problems, or fragile locators.
Q5What is the difference between smoke and regression tests?
Smoke tests are quick checks that basic functionality works. Regression tests are comprehensive tests to ensure nothing broke after changes.
SECTION 07Test yourself — glossary quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What is the most important term to learn first?
Learn "assertion" first — it is the foundation of every test. Then learn locators, waits, and test structure.
Do I need to memorize all terms?
No. Focus on understanding the concepts. You will learn the terms naturally as you practice.
Which tool should a beginner learn first?
Start with Playwright or Selenium. Playwright is easier to set up; Selenium is more widely used in enterprises.
What is CI/CD in simple terms?
CI/CD is an automated process that builds, tests, and deploys code whenever you make changes. It catches bugs early.
How do I start learning automation testing?
Learn a programming language (Java or Python), then a UI tool (Selenium or Playwright), then API testing. Build a project and apply for junior roles.
SECTION 09Related reads
Classroom & online · Noida
Start Your Automation Testing Career
Our Data Analytics Training Course includes a full automation testing module — Selenium, Playwright, API testing, and real projects.
₹15,500 · full programme- Complete automation testing syllabus
- Hands-on labs
- Framework project
- Weekday & weekend batches