ISQI CTFL2018 CTFL_Syll2018 Practice Test Engine: Try These 355 Exam Questions
Guaranteed Success in ISQI CTFL2018 CTFL_Syll2018 Exam Dumps
NEW QUESTION # 101
Which of the following is an appropriate reason for maintenance testing?
- A. Bugs found during system testing
- B. Bugs found during unit testing
- C. Bugs found during integration testing
- D. Bugs found in the field after upgrading the operation system
Answer: D
NEW QUESTION # 102
Which of the following Is an example of the absence-of-errors fallacy?
- A. Since testing found very few defects, the system certainly will be successful
- B. Other than trivial cases, it is not feasible to test all combinations of inputs and preconditions
- C. Over lime, running the same test cases do not find any defects
- D. A small number of modules contains the most defects
Answer: A
Explanation:
Explanation
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.
NEW QUESTION # 103
You are responsible for applying the correct technique (or a review of the requirements document for a project to develop a new software application. You identify the reviewers and the required roles, including the meeting leader, who is the requirements document author, and a separate role for a scribe. Additionally, you decide to take a relatively informal approach to the requirements review. The goal of the review is to find defects in the requirements document, such as omissions, inconsistencies, and duplications. Another goal of the review is to improve the software application's usability and accessibility by considering the various stakeholders' viewpoints.
Which of the following statements BEST describes this scenario?
- A. This scenario is using a pair review type and a checklist-based review technique
- B. This scenario is using a walkthrough review type and a perspective-based review technique
- C. This scenario is using a pair review type and a perspective-based review technique
- D. This scenario is using a walkthrough review type and a checklist-based review technique
Answer: B
Explanation:
Explanation
This scenario is using a walkthrough review type and a perspective-based review technique. A walkthrough is a type of review that is relatively informal and led by the author of the work product. A perspective-based review technique is a technique that involves reviewing the work product from different viewpoints or perspectives of various stakeholders. The scenario matches these descriptions, as it involves an informal approach, a meeting leader who is the author of the requirements document, and a goal of improving the software application's usability and accessibility by considering the various stakeholders' viewpoints. Option A is incorrect, as a pair review is a type of review that involves only two people, usually the author and another team member. Option C is incorrect, as a checklist-based review technique is a technique that involves reviewing the work product against a predefined list of items or criteria. Option D is incorrect, as it combines the incorrect descriptions of options A and C.
References: , Section 3.2.1, Section 3.2.4
NEW QUESTION # 104
Which of the following metrics is from the test design phase?
- A. Subjective confidence of testes in the system under test
- B. Percentage of test conditions covered by test cases
- C. Number of defects found and fix
- D. Number of test cases run / not run
Answer: B
Explanation:
Explanation
The percentage of test conditions covered by test cases is a metric from the test design phase, as it measures how well the test cases cover the test basis13. The other metrics are from the test execution phase or the test closure phase.
NEW QUESTION # 105
Which of the main activities of the fundamental test process does the task 'verify the test environment set up is
correct' relate to? [K1]
- A. Planning and control
- B. Evaluating exit criteria and reporting
- C. Implementation and execution
- D. Analysis and design
Answer: C
NEW QUESTION # 106
The following condition is given:
Integer x, y; IFx>0ANDx< 100
y = y + x; END-IF
Using boundary analysis for x. which test cases are required?
- A. -1,0. 100,101
- B. -500,-10,0.1,99.100.101,500
- C. 0, 1.99, 100
- D. -1,0.1,99.100, 101
Answer: D
Explanation:
Explanation
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
NEW QUESTION # 107
Which of the following is NOT an objective of testing?
- A. Gaining confidence about the level of quality of the software
- B. Finding defects
- C. Providing information for decision-making
- D. Analyzing and removing the cause of failures
Answer: D
Explanation:
Explanation
Testing has several objectives that aim to provide information and confidence about the quality and risk level of the software product and to support decision-making and improvement processes. Some of these objectives are:
Finding defects: Testing is the process of finding defects or failures in the software product that do not meet its requirements or expectations.
Providing information for decision-making: Testing is the process of providing information about the quality and risk level of the software product based on the observed behavior and results under certain conditions and assumptions. This information can help stakeholders make informed decisions about releasing, deploying, accepting, or improving the software product.
Gaining confidence about the level of quality of the software: Testing is the process of gaining confidence that the software product meets its requirements and expectations and provides value to the users and customers.
Analyzing and removing the cause of failures: Testing is not only the process of finding defects but also the process of analyzing and removing the cause of failures that lead to defects. This objective is related to debugging, which is a development activity that involves locating, diagnosing, and fixing errors in the code or design of the software product.
You can find more information about the objectives of testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 1, Section 1.2.
NEW QUESTION # 108
Which of the following would you NOT expect to see on an incident report from test execution?
- A. The version(s) of the software under test
- B. The test execution schedule
- C. Precise steps to reproduce the problem
- D. Expected results and actual results
Answer: B
NEW QUESTION # 109
While reporting a defect, which of the following indicates the level of business importance assigned to the defect?
- A. Severity
- B. Difficulty
- C. Priority
- D. Urgency
Answer: C
Explanation:
Explanation of Correct Answer: Priority indicates the level of business importance assigned to the defect, while severity indicates the degree of impact that a defect has on the development or operation of a component or system. Urgency is not a standard term used in defect reporting, and difficulty refers to the effort required to fix the defect.
References: Section 1.4.3.2, Section 5.3.2
NEW QUESTION # 110
Which from the following list are typically found to enable the review process to be successful? [K2] a. Each review has clear defined objectives b. The lower the number of defects, the better the review process c. The right people for the review objective are involved d. There is an emphasis on learning and process improvement e. Management are not involved in the process at all f. Checklists should not be used, as these slow down the process g. Defects found are welcomed and expressed objectively
- A. a, f and g.
- B. d, e and g.
- C. a, c and d.
- D. b, c and f.
Answer: C
NEW QUESTION # 111
After a record of poor quality software releases (incorrect menu selection options, new features that do not
work, users allowed to change security levels without administrator rights), you have been asked to review the
test capability in your company.
You have limited time to do the review before the next project, which type of testing would be MOST
appropriate to review first?
- A. Functional testing.
- B. Performance testing.
- C. Structural testing.
- D. Non-functional testing.
Answer: C
NEW QUESTION # 112
Which of the following would typically be identified using static analysis by tools? [K1]
- A. A variable set to the wrong value
- B. A potential infinite loop
- C. Memory leakage
- D. Spelling mistake on an error message
Answer: B
NEW QUESTION # 113
Which ONE of the following statements does NOT describe how testing contributes to higher quality?
- A. Software testing identifies defects, which can be used to improve development activities.
- B. Performing a review of the requirement specifications before implementing the system can enhance quality
- C. The testing of software demonstrates the absence of defects
- D. Properly designed tests that pass reduce the level of risk in a system
Answer: C
NEW QUESTION # 114
Which of the following BEST describes error guessing?
- A. Error guessing is a valid and useful white-box lest technique due to Its high degree ol statement coverage
- B. Error guessing involves building test cases based on the various experiences of developers, architects, users, and other stakeholders on project teams
- C. Error guessing involves designing tests based on experience, defect data, or common knowledge about why software fails
- D. Error guessing is a suitable test technique and can be used effectively in place of more formal techniques
Answer: C
Explanation:
Explanation
The correct answer is A, as it describes error guessing. Error guessing is an experience-based test technique that involves designing tests based on experience, defect data, or common knowledge about why software fails1. Error guessing can be used to complement other more formal test techniques by focusing on areas that are more likely to contain defects1. Option B is incorrect, as error guessing does not involve building test cases based on the various experiences of developers, architects, users, and other stakeholders on project teams, but based on the tester's own experience and knowledge1. Option C is incorrect, as error guessing is not a suitable test technique that can be used effectively in place of more formal techniques, but a supplementary technique that can be used in addition to more formal techniques1. Option D is incorrect, as error guessing is not a valid and useful white-box test technique due to its high degree of statement coverage, but an experience-based test technique that does not rely on the structure of the software1. References: 1, Section 4.2.6
NEW QUESTION # 115
What type of test design technique is the most effective in testing screen-dialog flows?
- A. Use case testing
- B. Statement testing and coverage
- C. State transition testing
- D. Boundary value testing
Answer: A
Explanation:
Explanation
Screen-dialog flows are sequences of screens and dialogs that represent the user interface and interaction of a system. Use case testing is a technique that uses use cases as a test basis to derive test cases1. A use case is a description of interactions between actors and a system to achieve a goal1. Use case testing is the most effective technique in testing screen-dialog flows, as it can capture the user requirements, scenarios, and expected outcomes of the system. Boundary value testing is a technique that uses boundary values as a test basis to derive test cases1. A boundary value is an input value or output value on the edge of an equivalence partition or at the smallest or largest value of a range1. Boundary value testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing numerical inputs and outputs. Statement testing and coverage is a technique that uses statements in the source code as a test basis to measure the coverage achieved by a test suite1. A statement is a minimal executable unit of source code1.
Statement testing and coverage is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing the internal logic and structure of the code. State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases1. A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions1. State transition testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing systems that have complex or dynamic behavior based on different states.
NEW QUESTION # 116
Which of the following does NOT represent one of the three triggers for maintenance testing an operational system?
- A. Data migration
- B. System retirement
- C. Introduction of a test management tool
- D. System modification
Answer: C
Explanation:
Explanation
The introduction of a test management tool does not represent one of the three triggers for maintenance testing an operational system, because it does not affect the functionality or performance of the system itself. Maintenance testing is triggered by system modification (such as corrective, adaptive, perfective or preventive changes), data migration (such as moving data from one platform or format to another), or system retirement (such as decommissioning or replacing an old system)1 .
NEW QUESTION # 117
Your company is developing a system with complex business rules and many branches in the structure of its code components. You need to choose one black box technique and one white box technique for test case design.
Which one of the following offers the BEST choice?
- A. Boundary value analysis and decision table testing
- B. Decision testing and equivalence partitioning
- C. Statement testing and exploratory testing
- D. Decision testing and decision table testing
Answer: A
NEW QUESTION # 118
Which of the following lists represents the correct sequence of the main activities of the fundamental test process (leaving out the activity of control which should take place in parallel to all the other activities)?
- A. Planning, analysis and design, execution, logging and reporting, regression testing
- B. Planning, analysis and design, implementation and execution, evaluation exit criteria and reporting, test closure activities
- C. Planning, analysis and reporting, design and implementation, execution, test closure activities, evaluating exit criteria.
- D. Planning, analysis, design and implementation, execution, logging, test closure activities, evaluating exit criteria.
Answer: B
NEW QUESTION # 119
Consider the following pseudo-code
How many minimum test cases are required to cover 100% Statement coverage and Decision coverage?
- A. 8 for Statement, 6 for Decision
- B. 6 for Statement, 8 for Decision
- C. 4 for Statement, 5 for Decision
- D. 5 for Statement, 5 for Decision
Answer: C
Explanation:
Explanation
To cover 100% statement coverage, we need to execute every statement in the code at least once. To cover
100% decision coverage, we need to execute every branch in the code at least once. The minimum number of test cases required to achieve both statement and decision coverage is 4 for statement and 5 for decision. Here is one possible set of test cases:
| Test Case | Input | Output | Statement Coverage | Decision Coverage | | TC1 | Walking = True, Midnight = False, Raining = False, Running = False | Take umbrella | S1, S2, S3, S4, S5 | D1-T, D2-T | | TC2 | Walking = False, Midnight = True, Raining = False, Running = False | Search light | S1, S2, S6, S7 | D1-F, D3-T | | TC3 | Walking = False, Midnight = False, Raining = True, Running = False | Take umbrella and search light | S1, S2, S6, S8, S9 | D1-F, D3-F, D4-T | | TC4 | Walking = False, Midnight = False, Raining = False, Running = True | Keep doing what you were doing | S1, S2, S6, S8, S10 | D1-F, D3-F, D4-F |
NEW QUESTION # 120
You need to test a vending machine for light drinks The machine has a button for each of the drinks it contains Pressing a button before inserting coins, will display the cost of the drink Pressing the same button after inserting enough coins will dispense the drink and provide change if needed) If the machine is out of the specific drink, and the button for this drink is pressed, the machine displays "Sold Out" (regardless if coins were inserted or not).
Which test technique is most suitable for this situation?
- A. Use-case testing
- B. Equivalence class testing
- C. Boundary value testing
- D. State transition testing
Answer: D
Explanation:
Explanation
State transition testing is the most suitable test technique for this situation. State transition testing is a technique that uses scenarios based on state diagrams to test the behavior of a system or component that can change its state in response to events or inputs. A state diagram is a graphical representation of the states that a system or component can be in, the events or inputs that can trigger a change of state (transitions), and the actions or outputs that can occur as a result of a change of state. In this case, the vending machine for light drinks can be modeled as a state diagram with states such as "idle", "coins inserted", "drink selected", "drink dispensed", "change returned", "sold out", etc., and transitions triggered by events such as "button pressed",
"coins inserted", "drink dispensed", "change returned", etc. State transition testing can help design test cases that cover all the possible states and transitions of the vending machine and verify its functionality and usability.
References: Certified Tester Foundation Level Syllabus, Section 4.5.1
NEW QUESTION # 121
Which of the following is a valid reason for writing test cases based on experience and intuition? [K1]
- A. Tests based on experience and intuition can supplement formal techniques
- B. Formal techniques require the use of expensive tools
- C. Use of formal techniques requires expensive training
- D. Only experience can ensure all functionality is covered
Answer: A
Explanation:
Explanation
A valid reason for writing test cases based on experience and intuition is C. Tests based on experience and intuition can supplement formal techniques. Experience and intuition are valuable sources of test ideas that can help testers to identify potential risks, errors, or scenarios that may not be covered by formal techniques.
Formal techniques are systematic methods that use rules or algorithms to derive test cases from the test basis (such as specifications, code, etc.). Formal techniques include black-box techniques (such as equivalence partitioning, boundary value analysis, etc.) and white-box techniques (such as statement coverage, decision coverage, etc.). Formal techniques can provide a high level of coverage and consistency, but they may not be able to capture all possible situations or behaviors of the system or component under test. Therefore, tests based on experience and intuition can supplement formal techniques by adding more diversity and creativity to the test cases. A detailed explanation of experience-based testing techniques can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 74-76.
NEW QUESTION # 122
Which of the following factors will MOST affect the testing effort required to test a software product? [K1]
- A. The number of staff available to execute tests
- B. The level of detail in the test plan
- C. The test estimation method used
- D. The requirements for reliability and security in the product
Answer: D
Explanation:
Explanation
The testing effort required to test a software product depends on various factors, such as the size and complexity of the product, the quality of the requirements and design documents, the testability of the product, the test strategy and scope, the test environment and tools, the skills and experience of the testers, and the quality expectations and standards of the stakeholders1. Among these factors, the requirements for reliability and security in the product will most affect the testing effort required to test a software product1. Reliability and security are quality attributes that measure how well a software product performs its intended functions under specified conditions and protects itself from unauthorized access or harm1. Testing for reliability and security requires more rigorous and thorough testing techniques, such as reliability testing, security testing, penetration testing, stress testing, etc1. These techniques may require more time, resources, tools, and skills to perform effectively1. Therefore, the requirements for reliability and security in the product will most affect the testing effort required to test a software product.
NEW QUESTION # 123
Which of the following is NOT a factor on which test estimation is dependent upon?
- A. Characteristics of the product
- B. Characteristics of the development process
- C. The outcome of testing of previous test cycle
- D. Defect debugging and resolution
Answer: C
Explanation:
Explanation
Test estimation is the process of predicting the effort, time, and resources required for testing a software system. Test estimation depends on several factors that influence the scope, complexity, and quality of testing.
Some of these factors are:
Characteristics of the product: This factor indicates how difficult or challenging it is to test the software system based on its size, functionality, reliability, usability, performance, security, etc.
Characteristics of the development process: This factor indicates how well or poorly the software system is developed based on the development methodology, standards, tools, techniques, etc.
Characteristics of the test process: This factor indicates how effective or efficient the testing process is based on the test strategy, plan, design, execution, evaluation, etc.
Characteristics of the test team: This factor indicates how skilled or experienced the test team is based on their knowledge, competence, motivation, communication, collaboration, etc.
The outcome of testing of previous test cycle is not a factor on which test estimation is dependent upon because it does not affect the effort, time, or resources required for testing the current test cycle. Rather, it is an outcome or consequence of test estimation that can provide feedback and lessons learned for improving future test estimations. You can find more information about test estimation in Software Testing Foundations:
A Study Guide for the Certified Tester Exam, Chapter 22.
NEW QUESTION # 124
When testing a mission critical system a high coverage should be achieved. Which of the following techniques should be implemented as a structural based coverage technique in order to achieve highest coverage?
- A. decision table
- B. use case testing
- C. multiple condition coverage
- D. statement coverage
Answer: C
NEW QUESTION # 125
For a given set of test-cases, which of the following is a benefit of running these tests with a test automation tool?
- A. The number of found bugs is reduced.
- B. The time spent on repetitive tasks is reduced
- C. Test coverage is increased.
- D. The total cost of the test project always decreases
Answer: B
Explanation:
Explanation of Correct Answer: A benefit of running tests with a test automation tool is that the time spent on repetitive tasks is reduced, as the tool can execute tests faster and more reliably than humans. Therefore, option D is correct. Option A is incorrect, as test coverage is not increased by using a test automation tool, but by designing more effective test cases. Option B is incorrect, as the number of found bugs is not reduced by using a test automation tool, but by improving the quality of the software under test. Option C is incorrect, as the total cost of the test project does not always decrease by using a test automation tool, as there are costs associated with developing and maintaining the automated tests.
References: Certified Tester Foundation Level Syllabus, Section 6.1
NEW QUESTION # 126
......
Test Engine to Practice CTFL_Syll2018 Test Questions: https://www.actualtorrent.com/CTFL_Syll2018-questions-answers.html
ISQI CTFL_Syll2018 Daily Practice Exam New 2023 Updated 355 Questions: https://drive.google.com/open?id=11K7S9T5Kdjxd9GO_byoGaA6L2LbAGKAk