BCS ISTQB Certified Tester Foundation Level CTFL 4.0 - CTFL4 Exam Practice Test

A. the tool may not be compatible with the development platform.

B. the tool may create additional development dependencies.

C. the tool may not be fit-for-purpose.

D. the tool will be owned and maintained by developers and replace testers.

A. This test quadrant contains smoke tests and non-functional tests (except usability tests). These tests are often automated.

B. This test quadrant is technology-facing and supports the team. These tests should be automated and included in the continuous integration (CI) process.

C. This test quadrant contains functional tests, examples, user story tests, user experience prototypes, API testing, and simulations. These tests check the acceptance criteria and can be manual or automated.

D. This test quadrant is business-facing and criticizes the system. It contains exploratory testing, usability testing, and user acceptance testing.

A. The support offered by a continuous integration tool is often leveraged by testers to automatically generate test cases from a model

B. The support offered by a test data preparation tool is often leveraged by testers to run automated regression test suites

C. The support offered by a bug prediction tool is often used by testers to track the bugs they found

D. The support offered by a performance testing tool is often leveraged by testers to run load tests

A. Traceability can be useful for determining the most suitable test techniques to be used in a testing project

B. Traceability can be useful for determining how many test basis items are covered by the corresponding tests

C. Traceability can be useful for assessing the impact of a change to a test basis item on the corresponding tests

D. Traceability can be useful to support the needs required by the auditing of testing

A. Static techniques can be used before all code is ready for execution

B. Static techniques find more detects then dynamic techniques.

C. Static techniques are always cheaper than dynamic techniques.

D. Static techniques can be used by inexperienced users.

A. Configuration management

B. Change management

C. Defect management

D. Risk management

A. Test objectives should be the same for all test levels, although the number of tests designed at various levels can vary significantly

B. Involvement of testers in work product reviews should occur as early as possible to take advantage of the early testing principle

C. Tests should be written in executable format before the code is written and should act as executable specifications that drive coding

D. Test levels should be defined such that the exit criteria of one level are part of the entry criteria for the next level

A. It is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model

B. It is not allowed because integration testing is a very important test level and ignoring i: means definite poor product quality

C. It is allowed because integration testing is not an important test level arc! can be dispensed with.

D. It is allowed as organizations can decide on men test levels to do depending on the context of the system under test

A. A3.B2. C1. D4

B. A2, B3, Cl, D4

C. A3, B2.C4. D1

A. Obstacles and their workarounds

B. New or changed risks

C. Test metrics to show the current status of the test process

D. A detailed assessment of product quality

A. Q4

B. Q3

C. Q1

D. Q2

A. Experienced testers, when applying error guessing, rely on the use of a high-level list of what needs to be tested as a guide to find defects

B. Experienced testers, when applying error guessing technique, can anticipate where errors, defects and failures have occurred and target their tests at those issues

C. Error guessing refers to the ability of a system or component to continue normal operation despite the presence of erroneous inputs

D. Error guessing is a system that adopts artificial intelligence to predict whether software components are likely to contain defects or not

A. Achieving full statement coverage and full branch coverage for a software product means that such software product has been fully tested and there are no remaining bugs within the code

B. Code-related white-box test techniques provide an objective measure of coverage and can be used to complement black-box test techniques to increase confidence in the code

C. Branch coverage is the most thorough code-related white-box test technique, and therefore applicable standards prescribe achieving full branch coverage at the highest safety levels for safety-critical systems

D. Code-related white-box test techniques are not required to measure the actual code coverage achieved by black-box testing, as code coverage can be measured using the coverage criteria associated with black-box test techniques