Free iSQI CTFL_Syll2018 Practice Exam with Questions & Answers

Functional testing is the most appropriate type of testing to review first, after a record of poor-quality software releases. Functional testing is a type of testing that verifies the functionality and behavior of the software against its requirements and specifications. Functional testing can help detect defects such as incorrect menu selection options, new features that do not work, users allowed to change security levels without administrator rights, etc. Functional testing can also help improve the user satisfaction and confidence in the software. Therefore, functional testing should be reviewed first to ensure that it is done effectively and efficiently, and that it covers all the relevant aspects of the software functionality.

References: Certified Tester Foundation Level Syllabus, Section 2.3 and 5.2.2

According to the syllabus, equivalence partitioning is a technique that divides the input data into partitions that are expected to be processed in the same way by the system under test. The partitions should be disjoint, meaning that they do not overlap. The answer C is correct because 50 and 60 are in the same partition of valid inputs that will pass the test. The other answers are incorrect because they contain values from different partitions.

References: Certified Tester Foundation Level Syllabus, Section 4.2.1, page 40.

 The percentage of planned test cases designed is not a common metric used for monitoring test preparation and execution, because it does not reflect the quality or completeness of the test cases or their alignment with the test objectives1 . The other options are common metrics used for monitoring test preparation and execution. The number of test cases passed and failed indicates the quality and status of the software under test1 . The number of test plan review comments indicates the quality and completeness of the test plan document1 . The percentage of tasks complete in test environment preparation indicates the progress and readiness of the test environment1 .

Incorrect interface specifications are most likely to be found by a review during static testing. A review is a type of static testing technique that involves a manual examination of a work product by one or more individuals who follow a defined process. A review can be applied to any work product, such as requirements specifications, design specifications, code, test cases, test plans, user manuals, etc. A review can help find defects and improve the quality of any work product at any stage of the software development lifecycle. Incorrect interface specifications are defects that affect the definition and communication of the interfaces between components or systems. These defects can be detected by reviewing the interface specifications document and comparing it with the requirements and design specifications.

References: Certified Tester Foundation Level Syllabus, Section 3.2.1

The correct answer is D, as DT1 and DT4 would achieve full coverage of the full decision table when combined with the test cases that have already been generated for rules 1 and 4. Decision table testing is a black-box test technique that uses a table to show combinations of inputs and their associated outputs1. In this case, the inputs are the account type, the amount entered, and the expected result. The outputs are the actions taken by the ATM system. The decision table has eight rules, each corresponding to a possible combination of inputs and outputs. The test cases that have already been generated for rules 1 and 4 are:

• TC1: Account = Checking, Amount = $600, Expected Result = Process the transaction
• TC4: Account = Savings, Amount = Not entered, Expected Result = Generate an error message

The additional test cases are:

• DT1: Account = Checking, Amount = Not entered, Expected Result = Generate an error message
• DT2: Account = Savings, Amount = $100, Expected Result = Process the transaction
• DT3: Account = Checking, Amount = $100, Expected Result = Process the transaction
• DT4: Account = Savings, Amount = $600, Expected Result = Generate an error message

To achieve full coverage of the full decision table, two more test cases are needed that cover the remaining six rules. DT1 and DT4 cover these rules, as shown in the table below:

Therefore, option D is the correct answer. Options A, B, and C are incorrect, as they do not cover all the rules in the decision table. References: 1, Section 4.2.5

The correct answer is A, as it explains a drawback of independent testing. Independent testing is a type of testing that is performed by a person or team that is not involved in the development of the software1. Independent testing can have many benefits, such as providing an objective view of the software quality, reducing conflicts of interest, and increasing the effectiveness and efficiency of testing1. However, independent testing can also have some drawbacks, such as being isolated from the rest of the development and project team1. This can lead to communication problems, lack of collaboration, and misunderstanding of requirements and expectations1. Option B is incorrect, as it does not explain a drawback of independent testing, but a benefit. Due to their differing backgrounds and perspectives, an independent test team may discover defects that the developers did not uncover1. This can improve the quality of the software and reduce the risk of failures in operation1. Option C is incorrect, as it does not explain a drawback of independent testing, but a strength. An independent test team may possess specializations in specific test types such as usability or security that enhance the overall effectiveness of the test team1. These test types may require specialized skills, tools, or environments that are not available to the developers or other testers1. Option D is incorrect, as it does not explain a drawback of independent testing, but a misconception. Having the business organization participate as an independent test team can benefit the overall testing effort since business participants can provide valuable feedback on the user requirements, expectations, and satisfaction1. However, business participants are often not trained nor experienced in testing, so they should not be the only source of independent testing1. They should be supported by professional testers who can apply appropriate test techniques and methods1. References: 1, Section 2.2

Having an independent test function in an organisation can improve defect finding during reviews and testing, because independent testers can provide a different perspective and have less bias than developers or other stakeholders. Independent testers can also focus on testing activities without being influenced by development pressures or deadlines12. The other options are not valid reasons for having an independent test function. Option B is more related to code reviews, which can be done by developers themselves or by peers. Option C is not beneficial, because communication between developers and testers is essential for effective testing and defect resolution. Option D is not directly related to the test function, but to the test management and reporting processes12.

TC1 - £23 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed. This answer can be derived from the decision table by matching the conditions of each test case with the corresponding rules and actions. For TC1, the conditions are: Loyalty Card holder = Y, 18 Holes = Y, Buggy/Cart Request = Y. These conditions match Rule 1, which has the actions: Green Fee = £18, Buggy Hire = £5, Total Charge = £23. For TC2, the conditions are: Loyalty Card holder = N, 18 Holes = N, Buggy/Cart Request = Y. These conditions match Rule 3, which has the actions: Green Fee = £16, Buggy Hire = Not Allowed, Total Charge = £16

Testers being involved in reviewing documents as soon as they are approved is not a characteristic of good testing, independent of the development life cycle model. Testers should be involved in reviewing documents as soon as drafts are available, not after they are approved, as this can help to detect defects early, improve communication and collaboration, and reduce rework and costs2 states this as follows:

Testers should be involved in reviewing documents such as requirements specifications or user stories as soon as drafts become available in order to provide early feedback on testability aspects such as clarity, consistency, completeness, correctness, unambiguity etc.

Early involvement of testers in reviewing documents can help to prevent defects from being introduced into later phases of development or testing by identifying potential issues or gaps before they become embedded in the system under test.

A, B, and C are characteristics of good testing, independent of the development life cycle model. Each test level having objectives specific for the test level (A) ensures that testing is aligned with the purpose and scope of each level and provides clear criteria for success. Every development activity being matched by a corresponding testing activity (B) ensures that testing is integrated with development and provides continuous feedback on quality and progress. Testers being involved in reviewing documents as soon as drafts are available © ensures that testing is performed early and throughout the life cycle and provides input on testability aspects.