Most Recent iSQI CTFL_Syll2018 Exam Questions & Answers

Test implementation and execution is the activity in the fundamental test process that includes test script generation.Test script generation is the process of creating executable test cases from test conditions and test data2defines this activity as follows:

Test implementation and execution has the following major tasks:

Develop and prioritize test cases, creating test data and writing test procedures.

Check test environment has been set up correctly.

Execute test cases, evaluate results and document deviations from expected results.

Use exit criteria to report on suitability of system under test.

Test closure activities (A) include finalizing and archiving test results, evaluating the test process, identifying areas for improvement, and celebrating achievements. Test analysis and design (B) include reviewing test basis, identifying test conditions, designing high-level test cases, and defining exit criteria. Test planning and control include defining test objectives, scope, strategy, resources, schedule, risks, and metrics.

Acceptance tests are the test types that call for involvement of an expert from the financial department for a new system that deals with all financial transactions in a company. Acceptance tests are tests conducted to determine if the requirements of a specification or contract are met by a system or software component prior to its delivery or deployment.Acceptance tests are usually performed by end users or customers who have domain knowledge and expertise in evaluating if the system meets their needs and expectations1defines acceptance tests as follows:

Acceptance Testing is a level of software testing where a system is tested for acceptability. The purpose of this test is to evaluate the system's compliance with the business requirements and assess whether it is acceptable for delivery.

Acceptance Testing is also known as User Acceptance Testing (UAT), End-User Testing, Operational Acceptance Testing (OAT) or Field (Acceptance) Testing.

Acceptance Testing is performed by end users or customers who have domain knowledge and expertise in evaluating if the system meets their needs and expectations.

A, C, and D are incorrect answers. Component testing, maintenance testing, and system testing are not test types that call for involvement of an expert from the financial department for a new system that deals with all financial transactions in a company. Component testing is testing of individual software components in isolation from other components, usually done by developers. Maintenance testing is testing of a modified system or component after changes have been made to it, usually done by testers. System testing is testing of an integrated system as a whole to verify that it meets specified requirements, usually done by testers.

The goal of statement testing is to increase the percentage of executable statements that are exercised by a test set.This is also known as statement coverage or line coverage3defines this as follows:

Statement Coverage (also known as Line Coverage) measures how many statements have been executed by your tests. It's calculated by dividing the number of executed statements by total number statements in source code file.

Statement testing does not aim to reduce the number of tests needed to test the system (A), assess the correctness of key statements in each module of the application (B), or assess the number of code statements needed to implement each feature (D).

The correct answer is A, as it provides the best test execution schedule that takes into account the priorities and technical and logical dependencies.A test execution schedule is a plan that defines the order and timing of test cases to be executed based on various factors such as dependencies, risks, priorities, and resources1. In this case, the factors are the priorities and technical and logical dependencies of the test cases.The priorities are the levels of importance or urgency assigned to the test cases, such as low, medium, or high1.The technical dependencies are the relationships between the test cases that require one test case to be executed before another test case can be executed1.The logical dependencies are the relationships between the test cases that make sense to execute one test case after another test case for better understanding or efficiency1. Option A provides the best test execution schedule that takes into account these factors, as it follows these rules:

Execute high priority test cases before medium or low priority test cases

Execute test cases that have technical dependencies in the correct order

Execute test cases that have logical dependencies in a sensible order

The following table shows how option A follows these rules:

Option B does not follow these rules, as it executes TC1 before TC2, which violates the technical dependency. Option C does not follow these rules, as it executes TC5 before TC6, which violates the logical dependency.Option D does not follow these rules, as it executes TC2 before TC3, which violates the technical dependency. Reference:1, Section 2.5

A functional test is a dynamic test for which the tests are based on the specification of the test object. This means that the test cases and test data are derived from the functional requirements, use cases, user stories, or other sources that describe the expected behavior and functionality of the system under test. A functional test is not focused on the efficiency of the system (that would be a performance test), nor is it a static comparison of test and requirements specification (that would be a review or inspection), nor is it based on the structure of the test object (that would be a structural test).

Certified Tester Foundation Level Syllabus - ISTQB Guru1, page 10

Certified Tester Foundation Level (CTFL) Syllabus - ASTQB2, page 65

A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer3, page 77