CTFL_Syll_4.0 無料問題集「ISQI ISTQB Certified Tester Foundation Level (CTFL) v4.0」

（A）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.

（B）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.

（C）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.

（D）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.

（A）Traceability between test basis items and thetest casesdesigned tocover them,enablesexperience-based test techniques to be applied

（B）Traceability between test basis items and thetest casesdesigned tocover them,enablesidentification of which test cases will be affected by changes to the test basisitems

（C）Traceability between test basis items and thetest casesdesigned tocover them,makes it possible to determine which test basis items have been covered by the executedtest cases

（D）Traceability can be established and maintained throughall test documentation for a giventest level, such as from test conditions through test cases to test scripts

（A）Static testing can benefit from using code-related white-box test techniques during code reviews

（B）White-box testing allows suggesting test cases for increasing coverage levels which are based on objective measures

（C）Black-box testing can benefit from using code-related white-box test techniques to increase confidence in the code

（D）Achieving full code coverage for a component or a system ensures that it has been fully tested

（A）The tester estimates the testing effort for individual iterations

（B）The tester assesses the testability of the user stories

（C）The tester writes acceptance criteria

（D）The tester breaks down user stories into smaller testing tasks

（A）Customer A: doesn't offer any upgrade; Customer B: doesn't offer any upgrade.

（B）Customer A: offers upgrade to Gold Luxury room; Customer B: doesn't offer any upgrade

（C）Customer A; doesn't offer any upgrade; Customer B: offers upgrade to Gold luxury room

（D）Customer A: offers upgrade to Silver room; Customer B: offers upgrade to Silver room.

（A）Acceptance testing

（B）Integration testing

（C）Structural testing

（D）Exploratory testing

（A）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

（B）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

（C）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

（D）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

（A）Define test environment requirements

（B）Evaluate test basis and test object

（C）Create test completion report

（D）Assess testability of test object

（A）Identification of the test object and test environment

（B）Description of the structure of the test team

（C）A concise title and a short summary of the defect being reported

（D）Expected results and actual results

（A）ATDD is the practice of running the automated acceptance tests as part of a continuous integration process

（B）Refactoring is a practice that is an integral part of TDD and is applied both to tests and to code written to satisfy those tests

（C）ATDD is a black-box test design technique that is applicable exclusively at acceptance test level

（D）BDD is a developer practice where business stakeholders are not usually involved as the tests are directly written at unit/component test level