CTFL-UK試験無料問題集「ISQI ISTQB Certified Tester Foundation Level (Syllabus 2011, GB only) 認定」

A. i, iv are true and ii is false

B. i, ii are true and iii, iv are false

C. ii, iii, iv are true and i is false

D. i, ii, iii are true and iv is false

A. Unit testing, system testing, acceptance testing, maintenance testing.

B. Unit testing, maintenance testing, system testing, acceptance testing.

C. Acceptance testing, system testing, maintenance testing, unit testing.

D. System testing, unit testing, acceptance testing, maintenance testing.

A. When there is enough information for sponsors to make an informed decision about release.

B. When every data combination has been exercised successfully.

C. When time and budget are exhausted.

D. When there are no remaining high priority defects outstanding.

A. 50% or 3/6

B. 100% or 6/6

C. 67% or 4/6

D. 83% or 5/6

A. To be based on an analysis of the structure of the component or system

B. To include both functional and non-functional testing

C. To be based on specifications

D. To be based on an analysis of the test basis documentation

A. (i) and (ii)

B. (ii) and (iii)

C. (i) and (iv)

D. (iii) and (iv)

A. That you have tested every combination of values of IF statements in the program

B. That you have tested every IF statement in the program

C. That you have tested every statement and every branch in the program

D. That you have tested every statement in the program

A. a & d

B. b & c

C. a & b

D. c & d

A. a, b and d are true; c and e are false

B. b, c and d are true; a and e are false

C. c, d and e are true; a and b are false

D. a is true; b, c, d and e are false

A. Security failures were the result of untested parts of code

B. The development team achieved complete statement and branch coverage but missed a serious bug in the MASPAR operating system

C. An error in the code was so obscure that you had to test the function with almost every input value to find its two special-case failures

D. All the above

A. Communication is limited between independent testers and developers.

B. Developers can lose a sense of responsibility for quality.

C. Developer and independent testing will overlap and waste resources.

D. Independent testers are too slow and delay the project schedule.

A. Find defects, such as memory leaks, while software is executing.

B. Monitor and report on how a system behaves under a variety of conditions.

C. Determine differences between files or databases.

D. Measure the percentage of specific types of code structure that have been exercised.

A. At integration testing and system testing levels only

B. At the component test level only

C. At all levels from integration testing to acceptance testing

D. At all test levels

A. To ensure the tools fits existing processes without change

B. To make a selection between alternative tools

C. To identify the requirements for using a tool

D. To assess whether the tool will be cost- effective

A. Independent testers within the development teams

B. Independent test specialists for specific test types, such as usability, performance or certification test specialists

C. Independent testers from the user community

D. Code tested by another developer from the development team

A. Provide support for the test team using the tool

B. Assessment of organisational maturity, strengths and weaknesses

C. Determine whether benefits will be achieved at reasonable cost

D. Estimate a cost-benefit ratio based on a firm business case

A. Time has run out

B. Both A and C

C. All faults have been fixed correctly

D. All the planned tests have been run

E. It depends on the risks for the system being tested

A. Correcting defects

B. Locating defects in the code

C. Ensuring no defects are present

D. Preventing defects

A. Component testing focuses on functional characteristics, whereas system testing focuses on functional and non-functional characteristics.

B. Component testing is the responsibility of the technical testers, whereas system testing typically is the responsibility of the users of the system.

C. Component testing verifies the functioning of software modules, program objects, and classes that are separately testable, whereas system testing verifies interfaces between components and interactions with different parts of the system.

D. Test cases for component testing are usually derived from component specifications, design specifications, or data models, whereas test cases for system testing are usually derived from requirement specifications, functional specifications or use cases.