ISTQB-CTFL試験無料問題集「ISTQB-Foundation Level 認定」

A. test design tool

B. unit test framework tool

C. monitoring tool

D. configuration management tool

A. Testing triggers a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

B. Testing identifies a defect that is caused by an error in the software, whereas debugging is concerned with finding the causes of this defect, analyzing these causes, and eliminating them.

C. Testing triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and eliminating them.

D. Testing triggers a failure that is caused by a defect in the software, whereas debugging is concerned with finding the causes of this failure (defects), analyzing these causes, and reproducing them.

A. Test monitoring and control

B. Test implementation

C. Test analysis

D. Test design

A. Identifying potential anomalies in the work product under review

B. Determining the people who will be involved in the review

C. Fixing the anomalies found in the work product under review

D. Recording the anomalies found during the review meeting

A. 0.50; 100; 150.200.350.500;

B. 0. 1.99, 100.200,201.499, 500;

C. 50; 100; 200. 1000

D. 50; 100; 250; 1000

A. Experience-based test techniques completely rely on the tester's past experience for designing test cases.

B. Experience-based test techniques tend to find defects that may be difficult to find with black-box and white-box test techniques and are often useful to complement these more systematic techniques.

C. Experience-based test techniques allow designing test cases that are usually easier to reproduce than those designed with black-box and white-box test techniques.

D. Experience-based test techniques provide more systematic coverage cnteria than black-box and white- box test techniques

A. I, III, IV

B. I, II, IV

C. I. III

D. I. IV

A. Release of the early draft of the low level project design of an loT application

B. Defect was found in a pre-released version of the customer service application

C. Delivery of the hot fix to mobile operating system and ensuring that it still works

D. Completion of architecture of the bank system

A. TC1 = 81 k€; TC2= 97k€; TC3=111k€; TC4=118k€

B. TC1 = 40k€; TC2= 46k€; TC3=51k€; TC4=53k€

C. TC1 = 79k€; TC2= 80k€; TC3=81k€; TC4=82k€

D. TC1 = 90k€; TC2= 110k€; TC3=125k€: TC4=140k€

A. The issue is related to performance efficiency, not functionality. Thus, as a functional tester, you should not open any defect report as all the functional tests passed

B. You should not open any defect report and inform the test manager that the devices on which you observed the issue should no longer be supported so that they will be removed from the requirements specification

C. You should not open any defect report as the problem is most likely due to poor hardware equipment on the devices where you observed the issue

D. You should open a defect report providing detailed information on which devices and by running which tests you observed the issue

A. Testing of disaster recovery and backup/restore is usually NOT part of acceptance testing.

B. Acceptance testing is the last level of testing performed prior to system release.

C. The main goal of acceptance testing is to build confidence in the system, not find defects.

D. The customers or system users are often responsible for the acceptance testing.

A. To set up the test environment.

B. To automate tests.

C. To prepare and acquire test data.

D. To coordinate the test strategy with project managers.

A. Validation is confirmation through the provision of objective evidence that the specified requirements have been met while verification is confirmation through the provision of objective evidence that the requirements for a specific intended use have been met

B. Verification is confirmation through the provision of objective evidence that the specified requirements have been met while validation is confirmation through the provision of objective evidence that the requirements for a specific intended use have been met

C. Verification is confirmation through the provision of subjective evidence that the specified requirements have been met while validation is confirmation through the provision of subjective evidence that the designs for a specific intended use have been met

D. Validation is confirmation through the provision of subjective evidence that the specified requirements have been met while verification is confirmation through the provision of subjective evidence that the designs for a specific intended use have been met

A. (-1.0,11.12.13,14,18.19)

B. (0.12.13.18.19)

C. (4.5.15.20)

D. (-1.0.12.13.18,19)

A. Test plans

B. Source code

C. Compiled code

D. Formal models