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

ai-ml-test-automation-mini
29 October 2021,
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
13 May 2021,
by a1qa
4 min read
How to attain in-sprint test automation to reinforce development processes
Learn how in-sprint test automation improves business workflows. Consider the top 5 essential steps to introduce it smoothly.
Test automation
12 April 2021,
by a1qa
5 min read
Watch out for 6 telecom trends and QA tips to implement them
In our article, we unleash the upcoming telecom trends and reveal how to be certain in introducing them correctly by applying QA practices.
Agile
Test automation
31 March 2021,
by a1qa
4 min read
QA scenario to introduce 6 eCommerce trends in 2021
Discover what trends will rule the eCommerce industry in 2021 and how QA can help implement them with confidence and ease.
Cybersecurity testing
Test automation
25 February 2021,
by a1qa
4 min read
9 QA points for delivering high-quality SaaS-based solutions
In the article, we’ve gathered 9 QA factors relying on the SaaS specifics that may help to perform SaaS testing with ease.
Cloud-based testing
Cybersecurity testing
Functional testing
Performance testing
Test automation
29 January 2021,
by a1qa
4 min read
3 do’s and 3 don’ts in BFSI software testing
Considering BFSI to be a fast-paced industry, how to keep up with such velocity? We’ve prepared 3 do’s and 3 don’ts that help sustain the rush and high software quality.
Functional testing
Mobile app testing
Test automation
18 December 2020,
by a1qa
4 min read
Top 5 QA and software testing trends in 2021: responding to a global situation with ease
Rapidly approaching 2021, a1qa proposes to have a closer look at the most influential trends empowering QA teams to perform even more effectively.
Agile
QA trends
Test automation
30 November 2020,
by a1qa
5 min read
Acumatica: ensuring sound business operations with well-tested ERP system
Internal business activities are advancing, while ERP systems’ usage is growing rapidly. Explore how to ascertain their accurate work through timely applying QA.
Big data testing
Cybersecurity testing
ERP testing
Functional testing
Performance testing
Test automation
13 November 2020,
by a1qa
5 min read
QA for media and entertainment
Read the article to explore why QA is a must for the media and entertainment sector and how to perform software testing effectively.
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.