CTFL-Foundation 無料問題集「ISQI ISTQB Certified Tester Foundation Level」

（A）A permanent tester who found most defects in the original system.

（B）A contract tester who has never worked for the organization before.

（C）A permanent programmer who reviewed some of the new code, but has not written any of it.

（D）A business analyst who wrote the original requirements for the system.

（A）None

（B）Planning and control

（C）Analysis and design

（D）Test closure activities

（A）A defect

（B）A fault

（C）A mistake

（D）An error

（E）A failure

（A）(ii) and (iii)

（B）(i) and (iv)

（C）(i) and (ii)

（D）(iii) and (iv)

（A）The responsibility of the users of a system.

（B）Concerned with the behavior of a whole system/product as defined by the scope of a development project.

（C）Triggered by modifications, migration or retirement of the software system.

（D）Used to search for defects in software modules that are separately testable.

（A）Planning, individual preparation, follow-up, re-work.

（B）Planning, kick-off, individual preparation, review meeting.

（C）Kick-off, planning, review meeting, re-work.

（D）Kick-off, review meeting, planning, follow-up.

（A）(ii) and (iii)

（B）(ii) and (iv)

（C）(i) and (ii)

（D）(iii) and (iv)

（A）P = 37, Q = 36, P=35, Q=36

（B）P = 42, Q = 43, P=42, Q=42

（C）P = 36, Q = 36, P=37, Q=35

（D）P = 24, Q = 20, P=24, Q=25

（A）Because 100% code coverage implies 100% coverage of requirements

（B）Because 100% code coverage guarantees that there are no coding errors

（C）Because code coverage can be used to ensure that all code is exercised by tests

（D）Because code coverage can ensure that all decisions are correctly implemented in the code

（A）The purpose of software testing is demonstrating the absence of defects in software products.

（B）Exhaustive software testing is, with enough effort and tool support, feasible for all software.

（C）For a software system, it is normally impossible to test all the input and output combinations.

（D）Automated tests allow better statements of confidence about the quality of software products.

（A）As soon as the UAT specification has been drafted

（B）At any time before UAT begins

（C）At the beginning of the project

（D）As soon as requirements have been approved

（A）To test all paths that users could take through the screen menu system

（B）To test all branches of component calls within the application call graph

（C）To ensure that 100% decision testing is achieved for each system component

（D）To ensure that users can navigate to all fields on the screen

（A）Yes, and it's also necessary to include all the exit combinations

（B）No, risk analysis and priorities should be used to focus testing efforts

（C）Yes, it's strongly recommended.

（D）Only the expert testers can make exhaustive tests.

（A）Using a keyword-driven testing approach to separate the actions and data from the tool's script

（B）Keeping expected results separate from the automation tool to allow the testers to check the results

（C）Selecting and automating scripts that test new functionality to find the most defects

（D）Ensuring that all data, inputs and actions are stored in the tool's script for ease of maintenance

（A）Provide support for the test team using the tool

（B）Assessment of organisational maturity, strengths and weaknesses

（C）Estimate a cost-benefit ratio based on a firm business case

（D）Determine whether benefits will be achieved at reasonable cost

（A）Design

（B）Decision table

（C）Requirements

（D）Code

（A）Test condition

（B）Test case

（C）Test procedure

（D）Test execution schedule