QUESTION: 37

Which of the following work products cannot be examined by static analysis?

Test plans
Source code
Compiled code
Formal models

Answer(s): A

Explanation:

Static analysis is the process of examining the work products of a software development or testing activity without executing them. Static analysis can be applied to various types of work products,

such as requirements, design, code, test cases, etc. However, test plans are not suitable for static analysis, because they are high-level documents that describe the test objectives, scope, strategy, resources, schedule, and risks of a testing project. Test plans are not executable or formalized in a way that static analysis tools can analyze them. Therefore, option A is the correct answer.

Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 2.2.1, page 20; ISTQB® Glossary v4.02, page 45.

Reveal Solution Next Question

QUESTION: 38

Confirmation testing is performed after:

a defect is fixed and after other tests do not find any side-effect introduced in the software as a result of such fix
a failed test, and aims to run that test again to confirm that the same behavior still occurs and thus appears to be reproducible
the execution of an automated regression test suite to confirm the absence of false positives in the test results
a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed

Answer(s): D

Explanation:

Confirmation testing is performed after a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed. Confirmation testing, also known as re-testing, is the process of verifying that a defect has been resolved by running the test case that originally detected the defect. Confirmation testing is usually done before regression testing, which is the process of verifying that no new defects have been introduced in the software as a result of changes or fixes. Therefore, option D is the correct answer.

Reference:

ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 2.4.1, page 28; ISTQB® Glossary v4.02, page 15.

Reveal Solution Next Question

QUESTION: 39

Which of the following statements about static testing and dynamic testing is true?

Unlike dynamic testing, which can be also performed manually, static testing cannot be performed without specialized tools
Static testing is usually much less cost-effective than dynamic testing
Unlike dynamic testing, which focuses on detecting potential defects, static testing focuses on detecting failures which may be due to actual defects
Both static testing and dynamic testing can be used to highlight issues associated with non- functional characteristics

Answer(s): D

Explanation:

This answer is correct because static testing and dynamic testing are both types of testing that can be used to highlight issues associated with non-functional characteristics, such as usability, performance, security, reliability, etc. Static testing is a type of testing that involves the analysis of software work products, such as requirements, design, code, or test cases, without executing them. Dynamic testing is a type of testing that involves the execution of software work products, such as code or test cases, using inputs and verifying outputs. Both static testing and dynamic testing can be applied to different test levels and test types, and can use different test techniques and tools, to evaluate the non-functional characteristics of the software product.

Reference:

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

Reveal Solution Next Question

QUESTION: 40

Which of the following is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development?

Test-Driven Development (TDD)
Acceptance Test-Driven Development (ATDD)
Behavior-Driven Development (BDD)
Domain-Driven Design (DDD)

Answer(s): C

Explanation:

This answer is correct because Behavior-Driven Development (BDD) is a test-first approach, where tests that express a shared understanding from stakeholders of how the application is expected to work, are first written in business-readable language (following the Given/When/Then format), and then made executable to drive development. BDD is a collaborative approach that involves testers, developers, business analysts, product owners, and other stakeholders in defining the expected behavior of the application using scenarios that describe the preconditions, actions, and outcomes of the application. BDD scenarios are written using a domain-specific language (DSL) that can be translated into executable test cases using tools such as Cucumber or SpecFlow. BDD aims to improve communication, collaboration, and feedback among the team members, and to deliver software that meets the customer's needs and expectations.

Reference:

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

Reveal Solution Next Question

Free CTFL4 Exam Braindumps (page: 10)

QUESTION: 37

Explanation:

Reference:

QUESTION: 38

Explanation:

Reference:

QUESTION: 39

Explanation:

Reference:

QUESTION: 40

Explanation:

Reference: