Process-driven Scripting
Process-driven scripting is a test automation approach in which automated scripts are organized according to defined business or testing processes rather than individual test cases.
“A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Process-driven Scripting?
This approach improves maintainability by aligning automation with standardized workflows and reusable process steps.
Workflow oriented: Scripts reflect business processes.
Reusability: Common process steps are shared across tests.
Maintainability: Process changes require fewer script updates.
Real World Example
A regulated product team is preparing a release where Process-driven scripting appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Process-driven scripting as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Process-driven scripting and similar ideas.
The page becomes useful in practice because Process-driven scripting is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Process-driven scripting in the context of ISTQB terminology?
Question 2
A tester needs to explain Process-driven scripting to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Process-driven Scripting. Test your understanding with topic-specific questions in our Mock Exams.