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 May. 14, 2026 (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.
A software company adopts the V-model as their development life cycle. Which of the following contains roles of a tester in this company?
The V-model is a development life cycle model that shows the relationship between each phase of development and its corresponding phase of testing. In this model, each level of testing (unit testing, integration testing, system testing, acceptance testing) has a corresponding level of development (component design, component integration, system design, requirements analysis). The model also shows that testing activities should start as early as possible in the development process and that each level of testing should be planned and designed in parallel with its corresponding level of development. Therefore, one of the roles of a tester in a software company that adopts the V-model is to coordinate the test strategy with the project managers who are responsible for planning and managing each phase of development. This role involves defining the scope, objectives, approach, resources, schedule, risks, and deliverables of each level of testing in alignment with the development plan and the project requirements. You can find more information about the V-model and test planning inSoftware Testing Foundations: A Study Guide for the Certified Tester Exam, Chapter 22.
Given the following requirement:
Which of the following statements is NOT correct?
The requirement given in the image specifies an additional fee of $3 that is charged during the weekend, with some exceptions and discounts based on the age of the visitors. To test this requirement, we can use boundary value analysis, which is a specification-based test technique that involves testing the values at or near the boundaries of an equivalence partition. An equivalence partition is a set of values that are expected to be treated in the same way by the system under test. For example, based on the requirement, we can identify the following equivalence partitions for the input age:
EP1: Age < 0 (invalid)
EP2: Age = 0 (valid, no charge)
EP3: 0 < Age < 7 (valid, no charge)
EP4: Age = 7 (valid, 20% discount)
EP5: 7 < Age < 13 (valid, 20% discount)
EP6: Age = 13 (valid, 20% discount)
EP7: 13 < Age < 65 (valid, full charge)
EP8: Age = 65 (valid, 50% discount)
EP9: Age > 65 (valid, 50% discount)
The boundary values for each equivalence partition are the values at or near the edges of the partition. For example, the boundary values for EP3 are 1 and 6. The boundary values for EP4 are 6 and 7. The boundary values for EP5 are 7 and 12. And so on.
To test this requirement using boundary value analysis, we need to select one value from each boundary and test it with different combinations of weekend and weekday. For example, we can select the following values:
BV1: Age = -1 (from EP1)
BV2: Age = 0 (from EP2 and EP3)
BV3: Age = 6 (from EP3 and EP4)
BV4: Age = 7 (from EP4 and EP5)
BV5: Age = 12 (from EP5 and EP6)
BV6: Age = 13 (from EP6 and EP7)
BV7: Age = 64 (from EP7 and EP8)
BV8: Age = 65 (from EP8 and EP9)
BV9: Age = 66 (from EP9)
We can then create test cases using these values and different combinations of weekend and weekday. For example:
TC1: Age = -1, Weekend = Yes -> Invalid input
TC2: Age = -1, Weekend = No -> Invalid input
TC3: Age = 0, Weekend = Yes -> No charge
TC4: Age = 0, Weekend = No -> No charge
TC5: Age = 6, Weekend = Yes -> No charge
TC6: Age = 6, Weekend = No -> No charge
TC7: Age = 7, Weekend = Yes -> $2.40 ($3 - 20% discount)
TC8: Age = 7, Weekend = No -> No charge
TC9: Age = 12, Weekend = Yes -> $2.40 ($3 - 20% discount)
TC10: Age = 12, Weekend = No -> No charge
TC11: Age = 13, Weekend = Yes -> $2.40 ($3 - 20% discount)
TC12: Age = 13, Weekend = No -> No charge
TC13: Age = 64, Weekend = Yes -> $3
TC14: Age = 64, Weekend = No -> No charge
TC15: Age = 65, Weekend = Yes -> $1.50 ($3 - 50% discount)
TC16: Age = 65, Weekend = No -> No charge
TC17: Age = 66, Weekend = Yes -> $1.50 ($3 - 50% discount)
TC18: Age =
66, Weekend = No -> No charge
Therefore, we need a minimum of18valid test cases to achieve100%boundary value coverage based on input age.
$3.01 is not a valid output boundary value because it is not a possible output value based on the requirement. The output values can only be $0, $1.50, $2.40, or $3 depending on the input age and weekend status.
You can find more information about boundary value analysis in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.2.
A "functional test" is...
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).
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
What type of test design technique is the most effective in testing screen-dialog flows?
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.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Jason Williams
3 days agoAmanda Parker
23 days agoAshley Wright
13 days agoMichael Hernandez
16 days agoJeffrey Smith
17 days agoKevin White
5 days agoDeborah Clark
1 day agoKristofer
1 month agoMaxima
2 months agoShizue
2 months agoLonna
2 months agoJohana
2 months agoGabriele
3 months agoLoise
3 months agoJules
3 months agoEvelynn
3 months agoMiriam
4 months agoAnna
4 months agoTalia
4 months agoJoanna
4 months agoRosendo
5 months agoLayla
5 months agoOmega
5 months agoMaybelle
5 months agoTasia
6 months agoJules
6 months agoEna
6 months agoLindsey
6 months agoMelvin
7 months agoTiffiny
7 months agoDonette
7 months agoShaquana
7 months agoLilli
7 months agoRebecka
8 months agoHaley
8 months agoMarci
8 months agoPaola
8 months agoEva
10 months agoFiliberto
10 months agoChanel
11 months agoDarrin
1 year agoLorriane
1 year agoCyril
1 year agoBrianne
1 year agoTawna
1 year agoMaryanne
1 year agoTommy
1 year agoDomonique
1 year agoWerner
1 year agoDortha
1 year agoRochell
1 year agoAlison
1 year agoChristiane
1 year agoJerry
1 year agoMarta
1 year agoJaclyn
1 year agoBettina
1 year agoPhyliss
1 year agoJenifer
1 year agoRolland
1 year agoLashaun
2 years agoAudra
2 years agoCasie
2 years agoRashad
2 years agoFletcher
2 years agoRonny
2 years agoLanie
2 years agoWilliam
2 years agoEzekiel
2 years agoElenor
2 years agoEladia
2 years agoDarrin
2 years agoTamesha
2 years agoYvonne
2 years agoFranchesca
2 years agoRosendo
2 years agoColette
2 years agoJesusa
2 years ago