QUESTION: 29

A typical objective of testing is to ensure that:

testing is used to drive the development of a software
a software has been tested using a combination of test techniques
there are no defects in a software that is about to be released
a software has been properly covered

Answer(s): B

Explanation:

This answer is correct because a typical objective of testing is to ensure that a software has been tested using a combination of test techniques, such as black-box, white-box, or experience-based techniques, that are appropriate for the test objectives, test levels, and test types. Testing using a combination of test techniques can increase the effectiveness and efficiency of testing, as different techniques can target different aspects of the software quality, such as functionality, usability, performance, security, reliability, etc. Testing using a combination of test techniques can also reduce the risk of missing defects that could be detected by one technique but not by another.

Reference:

ISTQB Foundation Level Syllabus v4.0, Section 2.3.1.1, Section 2.3.2

Reveal Solution Next Question

QUESTION: 30

Consider the following examples of risks identified in different software development projects:
[I]. The contrast color ratio for both normal text and large text of a website does not comply with the applicable accessibility guidelines, making it difficult for many users to read the content on the pages [II]. A development vendor fails to deliver their software system on time, causing significant delays to system integration testing activities that have been planned as part of a development project for a system of systems
[III]. People in the test team do not have sufficient skills to automate tests at the test levels required by the test automation strategy which does not allow production of an effective regression test suite [IV]. In a web application, data from untrusted sources is not subject to proper input validation, making the application vulnerable to several security attacks Which of the following statements is true?

[I] and [III] are product risks; [II] and [IV] are project risks
[I] and [IV] are product risks. [II] and [III] are project risks
[II], [III] and [IV] are product risks; [I] is a project risk
[IV] is a product risk; [I]. [II] and [III] are project risks

Answer(s): B

Explanation:

This answer is correct because product risks are risks that affect the quality of the software product, such as defects, failures, or non-compliance with requirements or standards. Project risks are risks that affect the project's schedule, budget, resources, or scope, such as delays, cost overruns, skill gaps, or scope changes. In this case, [I] and [IV] are product risks, as they relate to the accessibility and security of the software product, which are quality attributes. [II] and [III] are project risks, as they relate to the delivery time and the test automation skills of the test team, which are project factors.

Reference:

ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.1.1.1

Reveal Solution Next Question

QUESTION: 31

Following a risk-based testing approach you have designed 10 tests to cover a product risk with a high-risk level. You want to estimate, adopting the three-point test estimation technique, the test effort required to reduce the risk level to zero by executing those 10 tests. You made the following three initial estimates:
· most optimistic = 6 person hours
· most likely = 30 person hours
· most pessimistic = 54 person hours
Based only on the given information, which of the following answers about the three-point test estimation technique applied to this problem is true?

The final estimate is between 22 person hours and 38 person hours
The final estimate is exactly 30 person hours because the technique uses the initial most likely estimate as the final estimate
The final estimate is between 6 person hours and 54 person hours
The final estimate is exactly 30 person hours because the technique uses the arithmetic mean of the three initial estimates as the final estimate

Answer(s): A

Explanation:

The three-point test estimation technique is a method of estimating the test effort based on three initial estimates: the most optimistic, the most likely, and the most pessimistic. The technique uses a weighted average of these three estimates to calculate the final estimate, which is also known as the expected value. The formula for the expected value is:
Expected value = (most optimistic + 4 * most likely + most pessimistic) / 6 Using the given values, the expected value is:
Expected value = (6 + 4 * 30 + 54) / 6 Expected value = 30 person hours However, the expected value is not the only factor to consider when estimating the test effort. The technique also calculates the standard deviation, which is a measure of the variability or uncertainty of the estimates. The formula for the standard deviation is:
Standard deviation = (most pessimistic - most optimistic) / 6 Using the given values, the standard deviation is:
Standard deviation = (54 - 6) / 6 Standard deviation = 8 person hours The standard deviation can be used to determine a range of possible values for the test effort, based on a certain level of confidence. For example, using a 68% confidence level, the range is:
Expected value ± standard deviation
Using the calculated values, the range is:
30 ± 8 person hours
Therefore, the final estimate is between 22 person hours and 38 person hours, which is option A.

Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 2.3.2, page 24-25; ISTQB® Glossary v4.02, page 33.

Reveal Solution Next Question

QUESTION: 32

The acceptance criteria associated with a user story:

are often written in a rule-oriented format using the template referred to as "Given/When/Then"
are often documented following in rule-oriented format using the following template: "As a [role], I want [feature], so that I can [benefit]"
can be written in different formats and represent an aspect of a user story referred to as confirmation' of the so called "3 C's"
must be written in one of the two following formats: scenario-oriented or rule-oriented

Answer(s): C

Explanation:

The acceptance criteria associated with a user story are the conditions that must be met for the user story to be considered done and to deliver the expected value to the user. They are often written in different formats, such as rule-oriented, scenario-oriented, or table-oriented, depending on the nature and complexity of the user story. They represent an aspect of a user story referred to as confirmation, which is one of the so called "3 C's" of user stories. The other two aspects are card and conversation. Card refers to the concise and informal description of the user story, usually following the template: "As a [role], I want [feature], so that I can [benefit]". Conversation refers to the ongoing dialogue between the stakeholders and the team members to clarify and refine the user story and its acceptance criteria. Therefore, option C is the correct answer.

Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 3.2.2, page 35-36; ISTQB® Glossary v4.02, page 37.

Reveal Solution Next Question

Free CTFL4 Exam Braindumps (page: 8)

QUESTION: 29

Explanation:

Reference:

QUESTION: 30

Explanation:

Reference:

QUESTION: 31

Explanation:

Reference:

QUESTION: 32

Explanation:

Reference: