CTAL-TA_SYLL2019 · Question #39
In the recent past, you have learned that test automation just using capture & playback tooling, possibly enhanced with some test programming, has limitations. For the next banking project, that…
The correct answer is A. Define keywords to be implemented, eg, check balance. In a keyword-driven test automation approach, the Test Analyst is responsible for defining the keywords that represent the actions and expected outcomes of the test cases. The keywords are then implemented by a developer or a tool as reusable functions or scripts that can be…
Question
In the recent past, you have learned that test automation just using capture & playback tooling, possibly enhanced with some test programming, has limitations. For the next banking project, that will be run using Agile methods, you want to implement a keyword-driven test automation approach. You have already started to define some high-level test cases for the account transfer user story:
TC 1 transfer € 150 from Lars to Ann, verify Ann's balance to be € 150 TC 2 transfer € 300 from Tim to Ann, verify Ann's balance to be € 450 In the context of implementing the keyword-driven test automation approach, which of the following activities should now be conducted by the Test Analyst?
Options
- ADefine keywords to be implemented, eg, check balance.
- CSelect a tool to support keyword-driven testing
- DWork together with a developer to define a test automaton architecture
How the community answered
(43 responses)- A77% (33)
- C16% (7)
- D7% (3)
Explanation
In a keyword-driven test automation approach, the Test Analyst is responsible for defining the keywords that represent the actions and expected outcomes of the test cases. The keywords are then implemented by a developer or a tool as reusable functions or scripts that can be executed by the test automation framework. For example, the Test Analyst can define keywords such as "transfer", "check balance", "verify balance", etc. for the account transfer user story. These keywords can then be used to design test cases in a data-driven or table-driven format, such as: Driven Testing: A Detailed Tutorial With Examples (Section 1 and 2), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 4.2.1 and 4.2.2)
Topics
Community Discussion
No community discussion yet for this question.