CTFL_Syll2018 Leak Questions

 Using a keyword-driven testing approach to separate the actions and data from the tool’s script is the best approach to improve the way test automation tools are being used in your company, because it allows for more flexibility, maintainability, and reusability of automated test scripts1 . A keyword-driven testing approach uses keywords or commands to represent actions or data in the test scripts, which can be stored in external files or tables and accessed by the tool1 . The other options are not good approaches to improve the way test automation tools are being used in your company. Option A is not a good approach, because selecting and automating scripts that test new functionality to find the most defects does not consider the suitability, feasibility, and cost-effectiveness of automation1 . Option C is not a good approach, because ensuring that all data, inputs and actions are stored in the tool’s script for ease of maintenance makes the test scripts more rigid, complex, and difficult to modify1 . Option D is not a good approach, because keeping expected results separate from the automation tool to allow the testers to check the results reduces the efficiency and reliability of automation and increases the manual effort

Testing and debugging are two different activities that are related to finding and removing defects and failures in software. Testing is the process of evaluating software by applying test cases to find failures and provide information on its quality. Debugging is the process of finding, analyzing, and removing the causes of failures in software. Testing reveals failures, which are deviations of the actual behavior of the software from its expected behavior. Debugging removes defects, which are flaws in the software that cause failures.

References: Certified Tester Foundation Level Syllabus, Section 1.2.1

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

• A = 5, B = 4, C = 3, D = 2, E = 1
• A = 1, B = 2, C = 3, D = 4, E = 5
• A = 3, B = 4, C = 5, D = 2, E = 1
• A = 3, B = 2, C = 1, D = 4, E = 5

These four test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is four.

References: Certified Tester Foundation Level Syllabus, Section 4.3.1

A test procedure specification is a document that gives the precise steps needed in order to execute a test2. A test procedure specification defines how to run each test case or group of test cases in a specific order, including any preconditions, postconditions, inputs, outputs, actions, verifications, and expected results2. A test procedure specification can also include information about the test environment, tools, data, roles, responsibilities, risks, etc2. Therefore, a test procedure specification is a document that gives the precise steps needed in order to execute a test.