Free iSQI CTFL_Syll2018 Practice Exam with Questions & Answers | Set: 2

The correct answer is B, as it categorizes them as entry and exit criteria correctly. Entry criteria are conditions that must be met before testing can begin or continue with a specific activity or phase3. Exit criteria are conditions that must be met before testing can conclude or stop for a specific activity or phase3. The following table shows how each example can be categorized:

Therefore, option B is the correct answer. Options A, C, and D are incorrect, as they do not categorize them as entry and exit criteria correctly. References: 3, Section 2.4

The purpose of selecting a test technique is to increase the effectiveness of the test process by creating tests with higher chance of finding bugs. Test techniques do not define the number of regression cycles, nor are they the only way to test a software application. Test techniques may help reduce the number of tests, but that is not their primary goal.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 4.1.1, Page 29

Exploratory testing is by definition a reactive test approach, because it involves designing and executing tests based on the tester’s knowledge, experience and intuition, and reacting to the actual behavior and feedback of the system under test. Exploratory testing does not follow a predefined test plan or test cases, but rather adapts to the situation and learns from the results.

Using boundary analysis for x, the test cases are required to cover the values on and around the boundaries of x > 0 and x < 100. Therefore, the test cases should include -1, 0, 1, 99, 100, and 101. The value 0.1 is not a boundary value, and the values -500 and 500 are too far from the boundaries to be relevant.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 4.2.2, Page 34

Test plan is the test document where you would expect to find test exit criteria described. Test exit criteria are the conditions or requirements that must be met before testing can be completed or stopped. Test exit criteria are usually defined during test planning and control phase and evaluated during evaluating exit criteria and reporting phase. Test plan is a document that describes the scope, approach, resources, schedule, risks, metrics etc., for testing activities. Test plan also includes test exit criteria as part of its contents3 defines test exit criteria and test plan as follows:

Test exit criteria: The set of generic or specific conditions for permitting process exit criteria that are defined for each Test Level.

Test plan: A document describing the scope, approach, resources and schedule of intended test activities.

 A variable has the wrong numeric value passed into it is the type of defect that would not be typically found by using a static analysis tool, because it is a logical or functional error that depends on the context and requirements of the software13. A static analysis tool can detect syntactic or structural errors in the code, such as missing declarations, undefined variables, unused variables, or unreachable code13. The other options represent such errors that can be typically found by using a static analysis tool. Option A is an error where a variable is defined but is then not used, which indicates a waste of memory or a possible logic flaw13. Option B is an error where a variable is used in a calculation before it is defined, which can cause unpredictable results or exceptions13. Option D is an error where a variable is used but not declared, which can cause compilation or runtime errors

According to the syllabus, the absence-of-errors fallacy is a common misconception that finding and fixing defects will ensure the success of a system. This fallacy ignores the fact that there may be other factors that affect user satisfaction and system value, such as usability, functionality, performance, reliability, security, etc. The answer D is correct because it is an example of the absence-of-errors fallacy. Since testing found very few defects, the system certainly will be successful. This statement assumes that defect detection is the only criterion for system success, which is not true. The other answers are incorrect because they are not examples of the absence-of-errors fallacy, but rather facts or challenges related to testing.

References: [Certified Tester Foundation Level Syllabus], Section 1.2.1, page 11.

Functional and Structural tests are two different test design techniques, not test levels or test types. They can be applied at any test level (Unit, Integration, System, Acceptance) and for any test type (Functional, Non-functional, Regression, Maintenance). Therefore, option A is the correct answer. Option B is incorrect because Functional tests can be performed at any test level, not just Unit and Integration. Option C is incorrect because Functional and Structural are not test levels, but test design techniques. Option D is incorrect because Structural tests can be performed at any test level, not just Unit.

References: ISTQB Certified Tester Foundation Level Syllabus 2018 v3.1.1, Chapter 4.1.2 Test Design Techniques1

A typical characteristic of the walkthrough review type is that the meeting is led by the author. A walkthrough is a type of informal review that involves a presentation of a work product by the author to peers and other stakeholders for feedback and comments. The author leads the meeting and explains the work product to the participants, who can ask questions and make suggestions for improvement. The author may also record any issues or action items during the meeting. A walkthrough does not require formal preparation or follow-up by the participants, nor does it have defined entry and exit criteria.

References: Certified Tester Foundation Level Syllabus, Section 3.2.2

Managing the incidents in a spreadsheet posted on the intranet is the best option for a QA manager of a start-up company who needs to implement within a week a low cost incident management tool. A spreadsheet is a simple and flexible tool that can be used to record, track, and report incidents. Posting the spreadsheet on the intranet can make it accessible and visible to the relevant stakeholders. This option can be implemented quickly and cheaply, without requiring much training or maintenance3 suggests this as follows:

A spreadsheet is a common tool that can be used for incident management, especially for small or simple projects. A spreadsheet can be used to create an incident report template that includes the necessary information and fields for each incident. The spreadsheet can also be used to sort, filter, group, or analyze the incidents based on various criteria. The spreadsheet can be shared or published on a network or web location that can be accessed by the project team and other stakeholders.

A, C, and D are not good options for a QA manager of a start-up company who needs to implement within a week a low cost incident management tool. Managing the incidents through E-mails and phone calls (A) is not a good option, as it can be inefficient, unreliable, and inconsistent. E-mails and phone calls can be easily lost, overlooked, or forgotten, and they do not provide a centralized or structured way of recording, tracking, or reporting incidents. Purchasing and deploying an incident management tool © is not a good option, as it can be expensive, time-consuming, and complex. An incident management tool may require licensing fees, installation costs, configuration efforts, training sessions, and maintenance support. Documenting incidents on a large board in the lab (D) is not a good option, as it can be impractical, insecure, and incomplete. A large board in the lab may not have enough space or structure to document all the incidents in detail, and it may not be accessible or visible to all the stakeholders. A large board in the lab may also expose confidential or sensitive information to unauthorized people.