Blog

Keyword-driven testing methodology. Part 2

Let’s consider a very simple example to get a better idea of how KDT works. Imagine you have to test an application that adds two numbers. For the step of “defining business requirements and testing plan development,” you must determine what numbers can be put in and what interface elements might be used. Let it be positive integers. The app’s GUI has two text fields, a button and an inscription to show the result.
3 March 2015
Test automation
The article by Dmitry Tishchenko
Head of global business development at a1qa

The article was published on Computer Technology Review. Read the first part of the article here

According to the KDT approach, there are three roles in the automation testing process:

  • Test designer – creates the actual keyword-driven test cases, including pre- and post-conditions and keyword parameters. This is the role of a non-technical subject matter expert/business user.
  • Automation engineer – maintains the core framework and adapts it for any new customizations or enhancements. This is the role of a technical person who is well versed with coding and scripting language tools.
  • Test runner – serves as the continuous integration (CI) administration technician. This role does not require a purely technical person but requires understanding of what input data is needed in order for the automated script to run.

The KDT process includes the following steps:

  • Testing plan development (includes definition of automation testing keywords).
  • Automation testing scripts development.
  • Keywords implementation by automation engineer.
  • Launch of automation tests.
  • Implementation of automated tests in the regular pool (CI).

The picture below shows the different steps of the testing automation process for each of the aforementioned roles.

Let’s consider a very simple example to get a better idea of how KDT works. Imagine you have to test an application that adds two numbers. For the step of “defining business requirements and testing plan development,” you must determine what numbers can be put in and what interface elements might be used. Let it be positive integers. The app’s GUI has two text fields, a button and an inscription to show the result.

The “definition of automation testing words” step includes creation of a limited word set and the requirements for it. This step can be executed by a test designer.

We need three words possessing the following parameters:

  • “Edit”: two parameters (entry field name and entry text)
  • “Click result”: No parameters
  • “Verify”: one parameter (validation text)

The test designer describes the core of the tests – minimizing the quantity of used words. Using the KDT methodology, he/she analyzes tests on a high level. Therefore, it is easier for the test designer to identify the frequently repeated functions that should be automated for tests. As a result, the automation engineer receives a well-defined and simplified task.

For “testing scripts development,” we implement the words defined above, compose a test and input data:

  • Words implementation is a duty of the automation engineer. His/her task is to provide efficient execution of every test operation, even if the interface reacts slowly. He/she should also thoroughly validate the operation result and describe the words using “HOW TOs” for a test designer.
  • The tasks of test development and data preparation can be submitted to the test designer. He/she should provide tests for full-scale functionality coverage. To successfully fulfill this task, the test designer should understand the application requirements, choose the testing strategy and develop the cases.

The variant can be implemented by means of two test automating instruments – Robot Framework and the AutoIt plugin for robot framework.

The solution will include three tables and the code:

Whenever changes are made, everything should be verified immediately. You can apply high-level test tables to detect changes. As every keyword in KDT is used in multiple tests, it allows you to launch integration testing for already-checked keyword implementation. Thus, you can easily detect and fix all the issues caused by incorrect keyword usage.

As was mentioned, the above example is simplified, but the automation process for real-life projects is quite similar. However, with real projects involving test automation, testers handle many tasks at once. For example, before the test launch, the test runner should prepare the infrastructure and organize the multithreaded launch of automated tests, and the test designer should add information into the application database, as is shown in the picture below.

So what does all of this really mean?

To be continued… 

More Posts

a1qa-articles
31 January 2023,
by a1qa
5 min read
Best of 2022 by executives: 8 most visited a1qa blog posts
Let’s look back and revisit the most visited a1qa articles of 2022!
Quality assurance
Test automation
qa-trends
12 January 2023,
by a1qa
4 min read
The future of software testing: top 4 impactful trends that will dominate in 2023
Consider the major industry trends for the upcoming year to know how to improve current QA strategies and stay ahead of the curve.
QA trends
Quality assurance
Test automation
test-automation
7 December 2022,
by Dileep Marway
3 min read
Release at pace with test automation: What, why, and how to measure success?
An automation-first approach is key to enhancing testing capabilities and increasing overall operational efficiency. However, I would suggest justifying its implementation, so that it can deliver the promised value.
Quality assurance
Test automation
interview-with-dileep
28 November 2022,
by a1qa
9 min read
Interview with Dileep Marway on a series of articles “Agility and speed: Supercharging your business strategies with QA”
We cooperated with the VP of Engineering and Quality at SHL to present you with a series of his blog posts on: culture of happiness, test automation, and Agile-driven QA. Happy reading!
Agile
Quality assurance
Software lifecycle QA
Test automation
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

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.