ISTQB FOUNDATION 1

Which of following alternative describes NOT a major task of test implementation?

• Executing tests either manually or by using test execution tools
• Developing and prioritizing test procedures, and, potentially, creating automated test scripts.
• Creating test suits from test procedures and (if any) automated test scripts
• Preparing test data and ensuring it is properly loaded in the test environment.

Which of the following alternatives describes fundamental test process

• Test Planning - Test monitoring and control - test analysis - test design - Test implementation - test execution - test exit
• Test Planning - Test process control - test analysis - test design - Test implementation - test execution - test completion
• Test Planning - Test monitoring - test analysis - test design - Test implementation - test execution - test completion
• Test Planning - Test monitoring and control - test analysis - test design - Test implementation - test execution - test completion

Which of following statement describles correctly about software testing terms for problems in software?

• Errors or mistakes result in faults, which, when execute, may result in failures.
• Errors result in failures which, when executed, may result in incidents
• Human failures may result in defects, which, when executed, will result in incidents
• Problems during analysis and design my result in errors, which during execution my result in failures

Which of following alternative describles a general testing principle…

• Defect are evenly distributed through the system
• Repeating the same test cases over again in new version of software find less and less defects
• Test can prove that there are no defect
• If test show no defect, the the system is useful

Which of the following statements contains a valuable objective for a test team

• The goal is to fulfill all testing activity requirements as specified in the project handbook
• The goal is to cause as many failures as possible so that faults can be identified and corrected
• The goal is to prove that all faults are identified
• The goal is to prove that failures may not be caused any more by the remaining defects

You are running a written test which other testers have run previously. In addition, this test has found bugs previously, and those bugs have been confirmed to be fixed. The test manager has encouraged you to vary the specific way in which you run the test, such as the order of certain actions, the use of mouse versus hot-keys, and the particular input values, based on the way users will use in the system. Which of the following is a testing principle that could explain the test manager’s directive?

• Early testing
• Absence-of-errors fallacy
• Pesticide paradox
• Random testing

Which goal is usually not part of component testing?

• Testing correct functionality of the component
• Testing correct interactions between component.
• Testing completeness of the component’s functionality.
• Testing robustness of the component.

Which of alternatives describes the reasons of why there are different level of testing

<br>

A. Because every test level has a definite task and should concern the typical defects for that level

<br>

B. Because the test levels are executed by different personnel

<br>

C. Because defects can be found earlier by testing in many levels

<br>

D. Because execution of the earlier test levels tends to reduce over __ of later test levels with too many bugs.

<br>

E. In order to make project planning and follow-up easier, the testing objects are divided into test level

• A and B are true; C, D are false

• A, C and D are true; B and E are false

• B, C and D are true; A and B are false

• C, D and E are true; A and B are false

The following descriptions are related to acceptance testing. Which of the following alternative describes NOT true?

• Site acceptance testing is to determine whether or not a component or system satisfies the user/customer needs and fits within the business process, normally including hardware as well as software.
• Acceptance testing is formal testing with respect to users needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
• User acceptance testing verifies the fitness for use of the system and usability of business perspective
• Regulation acceptance testing is verifies the fitness for use of the system and usability of business perspective.
• Regulation acceptance testing is performed against any regulations that must be adhered to, such as governmental, legal or safety regulations

Which of the following alternative describes the main difference between “system testing” and “Acceptance testing”?

• System testing is done on the development platform, while acceptance testing is done on the customer platform
• System testing is done against the developers’ interpretation of the requirements, acceptance testing against customer understanding
• System testing concentrates on functional testing, while acceptance testing concentrates on nonfunctional testing
• Acceptance testing is a regression test for the changes implemented during system testing.