Free Preparation Discussions
MENU
iSQI CTFL_Syll2018 Exam Questions
- Topic 1: Apply equivalence partitioning to derive test cases from given requirements/ Identify typical objectives of testing
- Topic 2: Identify factors that influence the effort related to testing/ Describe the test activities and respective tasks within the test process
- Topic 3: Give examples of potential entry and exit criteria/ Describe the role of impact analysis in maintenance testing
- Topic 4: Explain the value of statement and decision coverage/ Distinguish between the root cause of a defect and its effects
- Topic 5: Recognize the different roles and responsibilities in a formal review/ Identify the tasks of a test manager and tester
- Topic 6: Recognize that functional, non-functional and white-box tests occur at any test level/ Identify the psychological factors that influence the success of testing
- Topic 7: Recall characteristics of good testing that are applicable to any life cycle model/ Explain how to derive test cases from a use cases
- Topic 8: Use examples to describe the value of static testing/ Apply a review technique to a work product to find defects
Free iSQI CTFL_Syll2018 Exam Actual Questions
Note: Premium Questions for CTFL_Syll2018 were last updated On Aug. 02, 2025 (see below)
An iPhone application identifies and counts all purchases of a particular product from a shopping website. The application incorrectly counts purchase attempts by including both failed attempts, and also those where the purchase was terminated by the user before completion. Testing has identified that the problem was located in the 'purchase identification' module, where the first stage in the purchasing process was counted, rather than a successful confirmed purchase.
Which of the following statements correctly identifies what has happened? [K2]
The application failed because of a defect in the purchase identification module caused by a programmer mistake or an error in the specification. A defect is a flaw or imperfection in a software product that causes it to fail to meet its requirements or expectations. A failure is an event or behavior of a software product that deviates from its requirements or expectations. An error is a human action or decision that produces a defect. A mistake is an incorrect action or decision that leads to an error. In this case, the application failed because it incorrectly counted purchase attempts, which was a defect in the purchase identification module. The defect was caused by either a programmer mistake (such as writing wrong code) or an error in the specification (such as defining wrong requirements). A detailed explanation of defects, failures, errors, and mistakes can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 5-6.
Which of the following is NOT an example of a typical risk-based testing activity?
Risk-based testing is an approach to testing that prioritizes and focuses on testing activities based on the level of risk associated with each feature or function of the system under test. Risk-based testing aims to optimize the use of time, resources, and techniques for testing by identifying and addressing the most critical and likely sources of failure or harm in the system under test. Some examples of typical risk-based testing activities are:
Brainstorming sessions are held with a wide variety of stakeholders to identify possible failures in the system: This activity is part of the risk identification process, which involves gathering information and opinions from different perspectives and sources to discover potential risks in the system under test.
Tests are prioritized to ensure that those associated with critical parts of the system are executed earlier: This activity is part of the risk analysis and evaluation process, which involves assessing the probability and impact of each risk and ranking them according to their severity and importance.
The focus of testing is shifted to an area in the system where tests find more defects than expected: This activity is part of the risk mitigation and monitoring process, which involves taking actions to reduce or eliminate the risks and tracking their status and progress.
The evaluation of a risk-management tool to decide which tool to use for future projects is not an example of a typical risk-based testing activity because it is not directly related to testing the system under test based on its risks. Rather, it is an example of a tool selection or evaluation activity, which involves comparing and choosing a tool that can support or enhance the testing process based on criteria such as functionality, usability, reliability, compatibility, cost, etc. You can find more information about risk-based testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 3, Section 3.4.
Which of the following is NOT an example of a common test metric?
Test metrics are quantitative measures that are used to monitor, control, and improve the test process and its outcomes. Test metrics can be collected at different levels of testing (test case, test suite, test project, etc.) and can be used for different purposes (planning, estimation, execution, evaluation, etc.). Some examples of common test metrics are:
Percentage of work done in test environment creation: This metric indicates how much effort has been spent on setting up and maintaining the test environment, which includes hardware, software, network, data, tools, etc., that are required for conducting the test activities.
Number of test cases run: This metric indicates how many test cases have been executed during a given period or phase of testing.
Deviation from test milestone dates: This metric indicates how much delay or ahead of schedule the test activities are compared to the planned dates.
Defect density: This metric indicates how many defects have been found per unit of size or functionality of the system under test.
Typically, exit criteria may consist of:
These are examples of exit criteria, which are the conditions that must be met before testing can be completed. Exit criteria may also include test coverage measures, residual risk assessment, or stakeholder approval. The other options are not exit criteria, but rather test planning activities.
Which of the following is NOT a factor on which test estimation is dependent upon?
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.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Eva
25 days agoFiliberto
1 months agoChanel
2 months agoDarrin
3 months agoLorriane
3 months agoCyril
4 months agoBrianne
4 months agoTawna
5 months agoMaryanne
5 months agoTommy
5 months agoDomonique
6 months agoWerner
6 months agoDortha
6 months agoRochell
7 months agoAlison
7 months agoChristiane
7 months agoJerry
7 months agoMarta
8 months agoJaclyn
8 months agoBettina
8 months agoPhyliss
8 months agoJenifer
8 months agoRolland
9 months agoLashaun
9 months agoAudra
9 months agoCasie
9 months agoRashad
9 months agoFletcher
10 months agoRonny
10 months agoLanie
10 months agoWilliam
10 months agoEzekiel
10 months agoElenor
11 months agoEladia
11 months agoDarrin
11 months agoTamesha
12 months agoYvonne
1 years agoFranchesca
1 years agoRosendo
1 years agoColette
1 years agoJesusa
1 years ago