Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?

You are working on a government system called “Making Tax Digital" or MTD for short. This system is being implemented to stop manual human input error and also to reduce fraudulent behaviour from companies when submitting their tax and VAT returns.

The key concept is that registered companies will need to use government recommended 3rd party software for their accounts and book keeping. These 3rd party applications will have a direct interface into the government’s main system for transactions and submissions.

You have been using a test execution tool successfully on the project so far. and have implemented a basic “capture/replay” approach to scripting.

The management have been encouraged with the automation so far, but want the following objectives to be met:

* Test cases added easily

* Reduction in the amount of scripts and script duplication

* Reduction in maintenance costs

Which scripting technique would be MOST suitable in this scenario in order to meet the objectives?
A . Linear scripting
B. Structured scripting
C. Data-driven scripting
D. Keyword-driven scripting

View Answer

Answer: D

Explanation:

Keyword-driven scripting allows for easier addition of test cases, less script duplication, and reduced maintenance costs which are the objectives outlined by management. This is because in keyword-driven scripting, you design test scripts using a set of predefined keywords, which represent actions that will be executed on the application under test. The keywords and the data associated with them are usually stored in tables (like a spreadsheet), making it easier to add, remove, or modify test cases.

Linear scripting (A) doesn’t provide flexibility in terms of reducing script duplication and maintenance costs as it involves writing a linear set of instructions for each test case.

Structured scripting (B) is useful when there is a need to create modular and reusable scripts, but it requires more complexity to implement than keyword-driven scripting and isn’t as easily adaptable for adding new test cases.

Data-driven scripting (C) is efficient when you need to test the same functionality with varying inputs and expected results, but it doesn’t inherently reduce script duplication or maintenance costs as much as keyword-driven scripting can. It also doesn’t directly aid in adding new test cases in an easy manner.