Keyword Driven Development

Question 1

ISTQB Definition of KDT (Keyword Driven Testing)

Answer 1

a scripting technique that uses data files to contain not only test data and expected results, but also keywords

Question 2

What is the The heart of Keyword Driven Testing (KDT)?

Answer 2

The idea that every application has a set of different tasks that need to be done to use the application.

Question 3

Definition of Keyword

Answer 3

Abstract statement of ‘what’ the system is supposed to do. A keyword is a business action or a step of a test case.

Question 4

functional (“the what”) tasks for almost any application rarely change.

Answer 4

the functional tasks that the users need to do with the application will almost always remain the same.

Question 5

The most right people that define the keywords that they need to test in the application.

Answer 5

Test analysts

Question 6

One of the most important prerequisites for implementing maintainable test scripts

Answer 6

is a good structure where the tasks to be performed remain abstract, such that they rarely change.

Question 7

Which is the layer that contains The test case described in abstract terms?

Answer 7

the test definition layer

Question 8

Which is the function of the test adaptation layer?

Answer 8

Interfaces between the test case and the physical GUI of the SUT.

Question 9

In which layer do we find the tool that is going to actually run the tests against the SUT?

Answer 9

The test execution layer

Question 10

Another name for keywords

Answer 10

Action Words.

Question 11

What is the containment of the KDT files?

Answer 11

test data, expected results and keywords.

Question 12

One advantage of the separation between a manual test case and the human tester when we use KDT principles:

Answer 12

The test case design is decoupled from the SUT

Question 13

What it is the division of labor that could exist in the automation team when we use the KDT principles?

Answer 13

o Test Analysts design test cases and write scripts using keywords, data, and expected results.
o Technical Test Analysts (automators) implement keywords and the execution framework needed to run the tests

Question 14

Advantages of the use of Keywords?

Answer 14

• Reuse of keywords in different test cases
• Improved readability of test cases (they look pretty much like manual test cases)
• Less redundancy
• Lower maintenance costs and effort
• Isolated execution of tests

Question 15

An advantage of the abstract language used in the writting of the keywords.

Answer 15

scripts using keywords can be written well before the SUT is available for testing (just like manual tests)

Question 16

How KDT allows the scalability of the work of a testing team over the TAA?

Answer 16

A few technical automators can support an unlimited number of test analysts

Question 17

What is the role of Low level keywords?

Answer 17

• Are implemented as Page Objects in the Test Adaptation Layer, they do the actions on the SUT.
• Used as parts of higher level keywords in the Test Library of the Test Definition Layer.

Question 18

What is the role of High level keywords?

Answer 18

• Are implemented in the Test Library

- Are used as test steps of Test Procedures in Test Execution Layer

Question 19

In which case the keyword structure can become quite complex?

Answer 19

When libraries of keywords use other keywords

Question 20

When keywords are interpreted by special supporting scripts?

Answer 20

when KDT is implemented using specialized tools such as Cucumber or RobotFramework.

Question 21

How the conversion works while we are implementing the test automation following the KDT principles?

Answer 21

Each keyword becomes the invocation of a function or method of the objects of the Test Library

Question 22

two ways of implementing KDT in practice

Answer 22

• top-down approach

- bottom-up direction.

Question 23

Top-down approach of KDT implementation

Answer 23

• Its first step is to design test cases as they would be designed for manual tests.
• Then the steps of these test cases are abstracted to become high level keywords, which may be decomposed into low level keywords or are implemented in a tool or a programming language.

Question 24

When the top-down approach is most cost-effective?

Answer 24

• when the Test Library already contains many functions/methods which perform tasks against the SUT.
• when automated scripts are converted from manual test cases

Question 25

bottom-up direction of KDT implementation

Answer 25

scripts are recorded by a tool (e.g., Selenium IDE) and then are refactored and restructured into a proper KDT test automation architecture.

Question 26

What it is the main advantage of the bottom-up direction strategy?

Answer 26

Allows test teams to quickly write several test automation scripts and run them against the SUT.

Question 27

In which ways he bottom-up direction exposes the automation project to a risk of future high maintenance efforts and costs?

Answer 27

• When we have more than twenty or thirty scripts using this quick-and-dirty approach without
  refactoring them to be a well-designed TAF.
• They are first scripted without following manual test cases and thus stand the risk of not being good tests (i.e., they may not actually mitigate important risks that need to be tested).

Question 28

Fine-grained keywords allow more specific scenarios

Answer 28

but at the cost of script maintenance complexity

Question 29

The more fine-grained a keyword is,

Answer 29

the more likely it is tied intimately to the interface of the SUT and the less abstract it is