- Keyword-Driven Testing (KDT) is a battle-tested method to speed up test automation development and cut down scaling costs in the long run.
- This article gives you the best practices that we’ve crystallized from our 20+ years of helping clients successfully build and maintain their KDT frameworks.
- To reap the full reward of KDT, you should 1) organize tests into self-contained test modules with clear test objectives, 2) separate Business-Level from Interaction-Level tests, and 3) architect a robust keyword library.
- As KDT is a widely adopted method, you can apply these best practices to many test automation tools including Robot Framework, Unified Functional Test, TestArchitect, TestComplete, Ranorex, etc.
We are pleased to introduce TestArchitect Team, the free — yet powerful — version of TestArchitect. The Team edition is equipped with all of the features needed in a smaller testing team.