iSQI Updated CTFL_Syll2018 Exam Questions and Answers by emilio

According to the syllabus, test execution scheduling is the process of assigning and ordering test cases or test procedures to be executed in a test cycle. Test execution scheduling should take into account the prioritisation and dependency of the test cases or test procedures, as well as the availability of test resources and environments. The answer B is correct because it best meets the prioritisation and dependency conditions given in the table. The answer B follows this logic:

• Start with the highest priority tests that have no dependencies, which are 5 and 7.
• Then, execute the tests that depend on 5 and 7, which are 4 and 3 respectively.
• Next, execute the remaining high priority tests that have no dependencies, which are 9 and 10.
• After that, execute the tests that depend on 9 and 10, which are 1 and 6 respectively.
• Finally, execute the low priority tests that have no dependencies, which are 8 and 2.

The other answers are incorrect because they either violate the dependency conditions or do not follow the prioritisation order. For example, answer A executes test 2 before test 10, which is not allowed because test 2 depends on test 10. Answer C executes test 6 before test 9, which is not allowed because test 6 depends on test 9. Answer D executes test 1 before test 9, which is not allowed because test 1 depends on test 9.

References: [Certified Tester Foundation Level Syllabus], Section 5.3.1, page 60-61.

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).

References:

• 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

If the fault in the code is contained in a small area, then it may cause the system to fail under certain circumstances, resulting in a defect1 . However, this is not a definite consequence, as it depends on whether the fault is executed or not. The other options are not definite consequences of this mistake either. Option A assumes that the system will always fail because of the fault, which may not be true if the fault is never executed or does not affect critical functionality1 . Option C assumes that there will be negative impacts on money, time, or business reputation because of the fault, which may not be true if the defect is minor or does not affect important stakeholders1 . Option D assumes that contractual requirements have not been met by testing because of the fault, which may not be true if testing has fulfilled its objectives and scope according to the contract1 .

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.