Keyword-Driven Testing


need to understand that the team still needs programmers dedicated to implementing and maintaining the framework.

The real benefit is the improved maintainability of the test scripts. The keyword approach follows in a longstanding tradition of modularizing the test automation so that it's easier to recover from user interface changes in the system under test. That benefit alone is sufficient to justify keyword-driven testing, even if all of the test designers are expert programmers.

Thanks to Mike Silverstein, Mike Kelly, and Carl Nagle for their early feedback on this article.

Further reading

  • FitNesse at
  • Just Enough Software Test Automation, Daniel J. Mosley and Bruce A. Posey, 2002
  • Integrated Test Design and Automation, Hans Buwalda, Dennis Janssen, Iris Pinkster, 2002

About the author

Danny R. Faught's picture Danny R. Faught

Danny R. Faught is the proprietor of Tejas Software Consulting, an independent consulting practice focusing on helping clients manage the quality of the software they produce.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!