Keyword driven testing approach
Blog

Keyword driven testing approach: why you should or shouldn’t use it

Keyword-driven approach in automated testing is one step away from behavior driven approach. It’s not far from behavior driven approach at comprehension standpoint but much more flexible and easy to re-factor. It is one step away from Object-driven approach, too.
10 April 2014
Test automation
The article by a1qa
a1qa

Keyword-driven approach in automated testing is one step away from behavior driven approach. It’s not far from behavior driven approach at comprehension standpoint but much more flexible and easy to re-factor. It is one step away from Object-driven approach, too.

You can use keywords as methods and “keyword arguments” as method arguments. So there is a possible usage of encapsulation, which could help re-using code and reduce time to write new tests. Actually, there are some tools like Robot Framework, which could use keyword driven, behavior driven and object-oriented approaches as well as data-driven one.

The main reason to use keyword driven approach in the project is maintenance costs and in some cases development costs. Maintenance costs are lower than in many other approaches because of easy keyword modification. To refactor or modify them your team should not have specific programming knowledge, the basics would be enough. Also because of inherited from object-oriented approaches modular structure of keywords they could be reused often, which cuts test development costs and lowers maintenance costs even more.

The reasons against the keyword driven approach are the same that could affect your test automation on the whole:

  1. Tests that you run only one time
  2. Tests that need to run ASAP
  3. Tests that based only on user experience

Keyword-driven approach could also be used in manual testing! This will give you flexible testing steps representation and test implementation. And one of the most exciting and debatable part of – you can combine manual steps with automated ones!

Pros

1.Re-usage of keywords

2.Divide et empera:

  • Test case implementation does not require learning specific tool or programming language, only SUT domain knowledge.
  • Keyword implementation does not require strong domain expertise and rely mostly on tool/programming language knowledge

3.Easy-to-implement abstraction layers

4.Less costly maintenance because of easy test modification, readability and keyword re-usage

Cons

1.Higher learning curve than with behavior driven testing

2.Division of responsibilities requires more intensive process management than with other approaches

Considering the approach benefits and requirements you can decide how to apply the method in test automation or manual testing to gain value.

The article is prepared by Yan Gabis.

More Posts

qa-trends-in-telecom
30 September 2022,
by a1qa
5 min read
4 telecom trends for 2023 and how to painlessly implement them with QA
It’s time to explore the telecom trends for the upcoming year. Let’s look at them together and also see the value that QA brings for their smooth deployment.
Cybersecurity testing
Migration testing
QA trends
Quality assurance
Test automation
ai-ml-test-automation-mini
15 September 2022,
by a1qa
4 min read
4 key QA activities to solve test automation challenges via AI and ML
How to address the difficulties caused by implementing test automation? Learn how to do it via applying AI and ML.
Test automation
why-do-bugs-get-missed
31 August 2022,
by a1qa
4 min read
Why do bugs get missed? Learn the problems and tips to avoid them
Still, finding overlooked bugs after the app goes live? Let’s find out why this happens and how to fix it.
Quality assurance
Test automation
30 June 2022,
by a1qa
4 min read
App software testing for telecom: What are the common issues telco providers face?
Facing problems with the quality of your telecom software products? Read more in the article and find out the ways to address them.
Cybersecurity testing
Performance testing
Test automation
Mobile app testing
31 May 2022,
by a1qa
4 min read
Mobile app testing guide: win the race with five-star software
Which aspects of mobile apps to test first to produce a really high-quality product? Find the answer to this and other questions related to mobile app testing in the article.
Cybersecurity testing
Functional testing
Mobile app testing
Performance testing
Test automation
Usability testing
Test automation in Agile
20 May 2022,
by a1qa
5 min read
Test automation in Agile and DevOps: Maximizing flexibility and speed
Global market tendencies and user behavior are changing rapidly, if not talking about the software itself. Familiar situation? Find out how to get ahead of the curve with test automation in Agile and DevOps.
Agile
Test automation
19 April 2022,
by a1qa
5 min read
What prevents companies from boosting eCommerce customer experience: 4 common mistakes
Dreaming of a flawless online shopping journey for your users? Explore 4 widespread situations that hamper achieving this goal.
Cybersecurity testing
Performance testing
Test automation
Usability testing
2 February 2022,
by a1qa
5 min read
Interview with Mike Urbanovich: How to build a robust test automation strategy?
The Head of testing department at a1qa answers the questions on how to smartly build a winning test automation strategy and talks about the advantages you may obtain with it.
Test automation
31 January 2022,
by a1qa
4 min read
Scriptless test automation: revealing the truth via 3 misconceptions
Planning to go scriptless but in doubt? Explore 3 delusions of codeless test automation and its benefits when introduced smartly.
Test automation

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.