iSQI CTFL_Syll2018 ISTQB Certified Tester Foundation Level Exam Practice Test

Answer : D

Equivalence Partitioning is a black-box test design technique that divides input data of a software module into partitions of equivalent data from which test cases can be derived. In this context, the valid equivalence partitions are:

Silver Tier: 0 to 400 Credits

Gold Tier: 401 to 800 Credits

Platinum Tier: 801 to 1400 Credits

Concierge Tier: 1401+ Credits

The test cases provided cover all these partitions:

TC1 covers the Silver Tier boundary at 400 Credits.

TC2 covers within the Gold Tier at 500 Credits.

TC3 covers the Gold Tier boundary at 800 Credits.

TC4 covers within the Concierge Tier at 1500 Credits.

Since all valid partitions are covered by the test cases, 100% of the valid Equivalence Partitions have been achieved.

Answer : C

According to the user story checklist, the user story must contain the reason for the need, which is usually expressed by using the word ''so that'' or ''because''. For example, the user story could be rewritten as:

User Story US2018 As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag and drop feature,so that I can easily manage my finances.

This way, the user story provides a clear value proposition and a justification for the need. The reason also helps to define the scope and priority of the user story, as well as to verify the acceptance criteria.

Answer : B

Maintenance testing is triggered bychangesto the software or its environment, or byretirementof the software or its environment1. Therefore, the events that would represent triggers for maintenance testing are:

Upgrading the production system's database for the latest Oracle release (a change to the environment)

Retirement of a live application that no longer has business benefit (a retirement of the software)

The other events are not triggers for maintenance testing, because they are either related to the development or testing process, or do not involve any change or retirement of the software or its environment. They are:

Migrating tests from a spreadsheet to the new test management tool (a change to the testing process)

An urgent fix to a new application before its initial release to production (a change to the software in development)

Simplifying the requirements to make them easier to analyse and review (a change to the requirements in development)

Answer : B

Traceability between the test basis and test work products means that there is a clear and documented relationship between the requirements, design, and other sources of test conditions, and the test cases, test procedures, and test results that are derived from them. This helps to ensure that the test work products are consistent, complete, and relevant to the test basis. One of the direct benefits of maintaining traceability is the ability to analyse the impact of changes in the test basis on the test work products, and vice versa. For example, if a requirement is changed, added, or deleted, traceability can help to identify which test cases, test procedures, and test results need to be updated, executed, or removed accordingly. Similarly, if a test result reveals a defect in the test basis, traceability can help to locate the source of the defect and determine the scope of the correction. Traceability also supports other benefits, such as measuring test coverage, reporting test progress, and evaluating test quality, but these are not direct benefits of maintaining traceability, rather they are outcomes of using traceability information for various purposes.Reference: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.1.2, p.23-241; ISTQB Glossary v4.0, p.672

Answer : C

In the context of software testing, the correct sequence of events typically starts with amistake, which is a human error made during the software development process. This mistake can lead to afaultin the code, which is a defect or bug that exists in the software. If this fault is executed, it may cause afailure, which is an instance where the software does not perform its intended function.

Answer : A

The correct answer is A, as it states that the Wideband Delphi estimation technique is an example of the expert-based approach.The Wideband Delphi estimation technique is a method of estimating testing effort or duration by using a structured group process that involves multiple experts2.The experts provide their estimates independently and anonymously, then compare and discuss them until they reach a consensus2.This technique is an example of the expert-based approach, which is an approach that relies on the knowledge and experience of experts to estimate testing activities2. Option B is incorrect, as it states that the Wideband Delphi estimation technique is an example of the metrics-based approach.The metrics-based approach is an approach that uses historical data and mathematical formulas to estimate testing activities2. This approach does not involve experts or group processes. Option C is incorrect, as it states that burndown charts used in Agile development is an example of the expert-based approach.Burndown charts are graphical tools that show the amount of work remaining versus time in an Agile project2. They are used to monitor and control testing progress and quality. They are not examples of the expert-based approach, as they do not rely on experts' opinions or estimates. Option D is incorrect, as it states that burndown charts used in Agile development is an example of the risk-based approach.The risk-based approach is an approach that uses risk analysis to prioritize and estimate testing activities2. This approach involves identifying and assessing risks based on their likelihood and impact.It does not involve burndown charts or Agile development. Reference:2, Section 2.6

Answer : D

The correct answer is D, as it describes exploratory testing.Exploratory testing is an experience-based test technique that involves simultaneous learning, test design, and test execution1. Exploratory testing may be used within defined time periods, during which the tester may follow a test charter as a guide.A test charter is a document that specifies the scope, objective, and approach of an exploratory testing session1.Option A is incorrect, as exploratory testing is not a suitable test technique that may replace both black-box and white-box test techniques, but a complementary technique that can be used along with other techniques1.Option B is incorrect, as exploratory testing does not require both solid specifications and much project time available for test execution, but can be used in situations where specifications are incomplete or changing and where time is limited1.Option C is incorrect, as exploratory testing is not a valid and useful black-box test technique since it focuses on test cases related to the architecture and design of a system, but an experience-based test technique that focuses on learning about the system and its behavior1. Reference:1, Section 4.2.6