CTFL_Syll2018 Exam Dumps - iSQI CTFL2018 Questions and Answers

A correct reason to apply test automation is when there are a lot of repetitive testing tasks, as test automation can reduce the effort and time required to execute them, and improve the consistency and accuracy of the results. The other options are not valid reasons to apply test automation, as they do not consider the benefits and risks of test automation, the suitability of the test object for automation, or the availability of resources and skills for automation.

References: Section 6.3.1, Section 6.3.2

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.

Regression testing is testing of an already tested program after modification to discover any defects introduced or uncovered as a result of changes in software or its environment. Regression testing ensures that previously working functionality still works after changes are made3 defines regression testing as follows:

Regression Testing is defined as a type of software testing to confirm that a recent program or code change has not adversely affected existing features.

Regression Testing is nothing but full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine.

I, III, IV, and V are incorrect statements about regression testing. Retesting of a fixed defect (I) is not regression testing, but confirmation testing or rework testing, which verifies that a specific defect has been resolved. Testing of new functionality in a program (III) is not regression testing, but functional testing or new feature testing, which verifies that new requirements are met by new code. Regression testing applies only to functional testing (IV) is not true, as regression testing can also apply to non-functional aspects such as performance or security. Tests that do not have to be repeatable, because they are only used once (V) are not regression testing, but exploratory testing or ad hoc testing, which are based on learning and discovery rather than predefined test cases.

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

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

Effort estimate depends on the budget of the project is the wrong statement about estimation of the test effort, because it confuses the cause and effect relationship between effort estimate and budget. Effort estimate does not depend on the budget of the project, but rather influences it. Effort estimate is an approximation of how much time and resources are needed for testing activities based on various factors such as scope, complexity, risks, quality, etc. . Budget is the amount of money that is allocated or available for testing activities based on the effort estimate . The other options are true statements about estimation of the test effort. Option A is true, because effort estimate can be inaccurate because the quality of the product under test is not known, which affects the number and severity of defects that need to be detected and fixed . Option B is true, because once the test effort is estimated, resources can be identified and a schedule can be drawn up, which are part of test planning . Option C is true, because experience based estimation is one of the estimation techniques that relies on the judgement and expertise of testers or other stakeholders who have previous knowledge or experience with similar projects .

 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

The correct logical order for the test cases is 3, 1, 4, 2, 6, 5. This order follows the logical sequence of actions that a user would perform to book a flight using a web-based airline booking system. The order also respects the dependencies between test cases, such as logging in before searching for flights or booking a flight before printing a confirmation receipt . The other options are incorrect logical orders for the test cases. Option A does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with confirming details and booking a flight before logging in or selecting a flight. Option B does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with selecting a flight before logging in or searching for flights. Option C does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with viewing selected items in My Flights before selecting any flights.

A test completion report for a test level typically includes a summary of all the testing activities that have been performed. It should detail any deviations from the original test schedule, including any changes in the planned duration or effort that were required to complete the test activities. This report serves as a record of what was tested, how it was tested, and any issues that were encountered.

 Exploratory testing would be a good test technique to use when under severe time pressure, because it is a type of experience-based technique that allows testers to design and execute tests based on their intuition, knowledge, and skills, without following a predefined test plan or test cases . Exploratory testing can be useful when testing time is very limited, as it can help to find important defects quickly and adapt to changing requirements or situations . The other options are not good test techniques to use when under severe time pressure. Option B is not a good option, because structure-based testing is a type of technique that requires analysing the code or design of the software under test to measure aspects such as code coverage, complexity, or coupling . Structure-based testing can be time-consuming and may not be feasible or effective when testing time is very limited . Option C is not a good option, because specification-based testing is a type of technique that requires analysing the requirements or specifications of the software under test to design test cases that verify the expected functionality or behaviour . Specification-based testing can also be time-consuming and may not be suitable or efficient when testing time is very limited . Option D is not a good option, because use case testing is a type of technique that requires analysing the use cases or scenarios of the software under test to design test cases that verify the end-to-end user interactions and outcomes . Use case testing can also be time-consuming and may not be relevant or effective when testing time is very limited .