Browse all topics
Marketing Operations Glossary

25 terms

Testing and release

Smoke testIs the system basically alive?
Incremental testingDoes the small change I just made work?
Regression testingDid the new change break anything that already worked?
Unit testDoes one isolated component behave correctly?
Integration testDo connected systems work together?
End-to-end test / E2EDoes the entire journey work from beginning to end?
User acceptance testing / UATDoes the finished system work for the people who requested it?
Quality assurance / QAThe overall process of preventing and finding defects.
Test caseOne defined scenario with an expected result.
Test planThe collection of scenarios, owners, environments, and expected results.
Happy pathThe normal journey where everything goes as expected.
Edge caseAn unusual but possible scenario.
Negative testConfirm the system correctly rejects or handles bad input.
A/B testRandomly compare two variants to identify which performs better.
Multivariate testTest combinations of several variables at once.
Holdout groupA group intentionally not exposed to the campaign.
Control groupThe baseline against which the treatment is measured.
Statistical significanceEvidence that a measured difference is unlikely to be random noise.
Practical significanceWhether the improvement is large enough to matter to the business.
IncrementalityResults caused by marketing that would not have happened anyway.
Feature flagA switch that turns functionality on for selected users without a full redeploy.
Canary releaseExpose a change to a small audience first to limit risk.
RollbackReturn to the last known working version.
Production / prodThe live environment used by real people and real data.
Sandbox / stagingA safe environment for building and testing.

Quick answers

Testing and release FAQs

What is included in the testing and release topic?

The testing and release topic is a collection of 25 marketing operations concepts used to plan, operate, govern, or evaluate this area of work. The grouping helps readers understand related language as a connected operating system rather than a list of isolated definitions.

For example, the topic includes Smoke test, Incremental testing, Regression testing, Unit test, Integration test. A professional can open those entries together when preparing a project, documenting a process, or aligning terminology with another team.

Which testing and release terms should I learn first?

Useful starting terms for testing and release include Smoke test, Incremental testing, Regression testing, Unit test, Integration test. These concepts provide an entry point, but the best sequence depends on the workflow, system, or decision you are responsible for.

For example, someone beginning a project in this area can read the five starting terms, compare their examples with the organization’s current process, and then follow the related-concept links to fill specific knowledge gaps.

How should I use these testing and release definitions?

Use these definitions as a shared starting point, then document the exact rules, owners, systems, thresholds, and exceptions used by your organization. A glossary creates common language, but operational agreement determines how the concept behaves in practice.

For example, a team can begin with the glossary definition of Smoke test, then add its own entry criteria, responsible role, source system, reporting field, and escalation path before using the term in automation or executive reporting.