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

A. Test plans

B. Source code

C. Compiled code

D. Formal models

A. The decision was right. Most of the bugs are easier to identify during the dynamic testing.

B. The decision was wrong. Static testing can find defects early in the development process, reducing the overall cost of testing and development

C. The decision was right. Static testing is usually redundant if a product is planned to go through a full- cycle of dynamic testing.

D. The decision was wrong. Ensuring quality mandates that static testing is performed after performing the dynamic testing.

A. 2,4,5

B. 1,3, 4.5

C. 1,2, 3. 4,5

D. 1,2,4

A. Incremental development model.

B. Iterative development model.

C. Sequential development model.

D. All the above

A. Management Review

B. Informal Review

C. Technical Review

D. Walkthrough

A. R100 000, R100 001, R500 000, R500 001.

B. R100 000. R500 000.

C. R99 999, R100 000, R499 999, R500 000.

D. R99 000, R500 001.

A. Status of defect

B. Description of the defect to enable reproduction.

C. Change history.

D. Conclusions, recommendations, and approvals.

A. A tester possesses professional pessimism while a developer is concerned with validating the product

B. A tester is concerned with finding defects while a developer is interested in designing solutions

C. A tester is interested in building solutions while a developer is concerned with verifying the product

D. A tester is concerned with verifying the product while a developer possesses professional pessimism

A. A to C, B to A, C to B, D to D and E to E

B. A to C, B to A, C to B. D to E and E to D

C. External interfacesE: Activities that can only be performed in the system under certain conditions defined by outside procedures and constraints.

D. A TO A, B TO B, CTOB, DTO E AND E TO D

E. Business rulesD; Description of the connections between the system to be developed and the outside world.

F. How the system performs the specific behaviour.
8: Quality characteristicsB: A sequence of actions between an external actor and the system, to accomplish a specific goal or business task.

G. A to E, B to A, C to B, D to C and E to D

H. ScenariosC: The externally observable behaviour with user actions as input operating under certain configurations.

A. All testing levels are applicable, independent of which software development life-cycle process (V- model. iterative, incremental) is used.

B. Acceptance testing is applicable for all software development models.
Component and system testing are applicable only for the V-model.

C. Integration and system testing are applicable when V-model is used.
Component and acceptance testing are applicable when iterative development models are used.

D. All the testing levels are applicable to V-model for software development.
Only acceptance testing is applicable for iterative models.

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. the tool may create additional development dependencies.

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

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

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

A. The author of the work product to be reviewed leads the review meeting.

B. All participants in the review are aware they will be evaluated based on the defects they will find

C. Review metrics must be collected to improve the review process

D. All participants in the review are trained to deal with the review type and its objectives.

A. Checklist-based testing is restricted to non-functional testing, including usability, performance, and security test

B. Checklist-based testing may involve a list of tests based on what is important to the user as well as an understanding of why and how software fails

C. Checklist-based testing includes formal tests from detailed lists of test conditions, allowing much repeatability

D. Checklist-based testing, while popular, provides little consistency and few guidelines concerning test case development

A. Choosing which standards to follow during the review process is usually made during review planning.

B. Various review techniques that may be applied by participants during individual review are described in the ISO/IEC/IEEE 29119-3 standard.

C. Individual review is only mandatory when the size of the work product under review is too large to cover at the review meeting

D. One of the main goals of the review meeting is to make sure that all participants are aware of their roles and responsibilities in the review process

A. produce tests that are less subject to human errors

B. increase test process efficiency by facilitating management of defects

C. avoid performing exploratory testing

D. demonstrate the absence of defects

A. Confirmation testing ensures the entire system functions as expected, whereas regression testing focuses only on modified components.

B. Confirmation testing verifies all system requirements, while regression testing ensures that no additional test cases are needed.

C. The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been successfully fixed. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

D. Regression testing and confirmation testing are interchangeable and serve the same purpose.

A. A detailed report on the test results after the test project is completed.

B. A detailed analysis of the defects found and their causes.

C. The budget and schedule for the test project.

D. A list of test logs from the test execution.

A. All the tests should be automated and run as part of the continuous integration process with every software change

B. Test analysis and design for any test levels should begin as soon as coding is complete, and all system components are available for testing

C. Each test level should have its own specific test objectives that should be consistent with the software development lifecycle phase or type of activities it addresses.

D. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.