KEYWORD DRIVEN TESTING IN THEORY & PRACTICE
summary
Explains why keyword-driven testing splits work into keyword authors who implement actions in code and verification engineers who assemble test cases from those actions, and shows a concrete stack: Robot Framework with custom Python/Java libraries, the Selenium library for web steps, Jenkins scheduling and QC reporting plugins. Demonstrates suite setup/teardown, cloud VM deploy and destroy per suite, fail-fast behavior that stops on step failure, and a repo workflow where only the automation team commits reviewed keyword code.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:16Keyword driven testing concept
- 11:28Robot Framework overview
- 17:35Nokia’s implementation
- 24:52Use cases and conclusion
related talks
34mBasics of Robot Framework
14mTest Automation Framework Design and Implementation
48mTest Automation - A Systems Thinking Approach
26mProduct-independent automation framework
46mBehavior-Driven Development in Python
58mTesting Strategy - New Model, Better Outcomes
45mBehaviour Driven Development and Behat: Telling Stories Through Code
54mDomain Driven Testing: Know What You're Doing