Software Testing ISTQB Foundation Dumps.

1. Non-functional system testing includes:

Testing to see where the system does not function properly

Testing quality attributes of the system including performance and usability

Testing a system feature using only the software required for that action

Testing a system feature using only the software required for that function

Testing for functions that should not exist

Non-functional system testing focuses on evaluating the quality attributes of the system, such as its performance and usability. This type of testing ensures that the system meets the non-functional requirements and performs well under different conditions. It involves assessing factors like response time, scalability, reliability, security, and user experience. By conducting non-functional system testing, organizations can identify potential issues or bottlenecks that may affect the system's overall performance and user satisfaction.

Explanation

Non-functional system testing focuses on evaluating the quality attributes of the system, such as its performance and usability. This type of testing ensures that the system meets the non-functional requirements and performs well under different conditions. It involves assessing factors like response time, scalability, reliability, security, and user experience. By conducting non-functional system testing, organizations can identify potential issues or bottlenecks that may affect the system's overall performance and user satisfaction.

2. Regression testing should be performed:

v) every week

w) after the software has changed

x) as often as possible

y) when the environment has changed

z) when the project manager says

V & w are true, x – z are false

W, x & y are true, v & z are false

W & y are true, v, x & z are false

W is true, v, x y and z are false

All of the above are true

Regression testing should be performed after the software has changed (w) because when changes are made to the software, it is important to ensure that the existing functionalities have not been affected. It should also be performed when the environment has changed (y) because changes in the environment can have an impact on the software's behavior. Performing regression testing every week (v) or as often as possible (x) may not be necessary or practical in all cases. Regression testing should not be performed solely based on the project manager's decision (z) as it should be based on objective criteria. Therefore, the correct answer is w & y are true, v, x & z are false.

Explanation

Regression testing should be performed after the software has changed (w) because when changes are made to the software, it is important to ensure that the existing functionalities have not been affected. It should also be performed when the environment has changed (y) because changes in the environment can have an impact on the software's behavior. Performing regression testing every week (v) or as often as possible (x) may not be necessary or practical in all cases. Regression testing should not be performed solely based on the project manager's decision (z) as it should be based on objective criteria. Therefore, the correct answer is w & y are true, v, x & z are false.

3. Testing should be stopped when:

All the planned tests have been run

Time has run out

All faults have been fixed correctly

Both a) and c)

It depends on the risks for the system being tested

Testing should be stopped when it depends on the risks for the system being tested. This means that the decision to stop testing should be based on the level of risk associated with the system. If the risks are deemed acceptable and all planned tests have been run, then testing can be stopped. However, if there are still unresolved faults or if time has run out but the risks are still high, testing may need to continue until the risks are mitigated. The decision to stop testing should prioritize the safety and reliability of the system.

Explanation

Testing should be stopped when it depends on the risks for the system being tested. This means that the decision to stop testing should be based on the level of risk associated with the system. If the risks are deemed acceptable and all planned tests have been run, then testing can be stopped. However, if there are still unresolved faults or if time has run out but the risks are still high, testing may need to continue until the risks are mitigated. The decision to stop testing should prioritize the safety and reliability of the system.

4. Which of the following is NOT part of configuration management:

Status accounting of configuration items

Auditing conformance to ISO9001

Identification of test versions

Record of changes to documentation over time

Controlled library access

Auditing conformance to ISO9001 is not part of configuration management because ISO9001 is a quality management standard that focuses on ensuring consistent quality in products and services. Configuration management, on the other hand, is the process of managing and controlling changes to a system's configuration items. While auditing is an important aspect of quality management, it is not directly related to the management of configuration items and their changes.

Explanation

Auditing conformance to ISO9001 is not part of configuration management because ISO9001 is a quality management standard that focuses on ensuring consistent quality in products and services. Configuration management, on the other hand, is the process of managing and controlling changes to a system's configuration items. While auditing is an important aspect of quality management, it is not directly related to the management of configuration items and their changes.

5. What is the purpose of test completion criteria in a test plan:

To know when a specific test has finished its execution

To ensure that the test case specification is complete

To set the criteria used in generating test inputs

To know when test planning is complete

To plan when to stop testing

The purpose of test completion criteria in a test plan is to plan when to stop testing. This means that the criteria are used to determine when the testing process has been completed and it is time to move on to the next phase or release the product. It helps in defining the conditions or requirements that need to be met in order to consider the testing phase finished. This ensures that testing is not continued indefinitely and allows for a systematic and efficient approach to testing.

Explanation

The purpose of test completion criteria in a test plan is to plan when to stop testing. This means that the criteria are used to determine when the testing process has been completed and it is time to move on to the next phase or release the product. It helps in defining the conditions or requirements that need to be met in order to consider the testing phase finished. This ensures that testing is not continued indefinitely and allows for a systematic and efficient approach to testing.

6. Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries:

1000, 5000, 99999

9999, 50000, 100000

10000, 50000, 99999

10000, 99999

9999, 10000, 50000, 99999, 10000

The given answer, 10000, 50000, 99999, represents valid equivalence classes and valid boundaries for the order numbers on the stock control system. 10000 is the lower boundary value, 50000 is an arbitrary value within the valid range, and 99999 is the upper boundary value. This combination of inputs ensures that the tests cover both the valid equivalence classes (values within the valid range) and the valid boundaries (minimum and maximum values).

Explanation

The given answer, 10000, 50000, 99999, represents valid equivalence classes and valid boundaries for the order numbers on the stock control system. 10000 is the lower boundary value, 50000 is an arbitrary value within the valid range, and 99999 is the upper boundary value. This combination of inputs ensures that the tests cover both the valid equivalence classes (values within the valid range) and the valid boundaries (minimum and maximum values).

7. Deviation from the specific or expected behavior, this is called:

An error

A fault

A failure

A defect

A mistake

When there is a deviation from the specific or expected behavior, it is referred to as a failure. This implies that something did not go as planned or as it should have. It suggests that there was a breakdown or inability to perform a task or meet a certain standard. The term "failure" encompasses a broader scope compared to the other options provided, as it can include errors, faults, defects, or mistakes that lead to the failure itself.

Explanation

When there is a deviation from the specific or expected behavior, it is referred to as a failure. This implies that something did not go as planned or as it should have. It suggests that there was a breakdown or inability to perform a task or meet a certain standard. The term "failure" encompasses a broader scope compared to the other options provided, as it can include errors, faults, defects, or mistakes that lead to the failure itself.

8. Consider the following statements about early test design:

i. early test design can prevent fault multiplication

ii. faults found during early test design are more expensive to fix

iii. early test design can find faults

iv. early test design can cause changes to the requirements

v. early test design takes more effort

I, iii & iv are true. Ii & v are false

Iii is true, I, ii, iv & v are false

Iii & iv are true. i, ii & v are false

I, iii, iv & v are true, ii us false

I & iii are true, ii, iv & v are false

Early test design can prevent fault multiplication by identifying and addressing potential faults early in the development process. Additionally, early test design can find faults before they become more expensive to fix later on. It can also cause changes to the requirements as issues are discovered and addressed. However, it does not necessarily take more effort and faults found during early test design are not necessarily more expensive to fix. Therefore, statements i, iii, and iv are true, while ii and v are false.

Explanation

Early test design can prevent fault multiplication by identifying and addressing potential faults early in the development process. Additionally, early test design can find faults before they become more expensive to fix later on. It can also cause changes to the requirements as issues are discovered and addressed. However, it does not necessarily take more effort and faults found during early test design are not necessarily more expensive to fix. Therefore, statements i, iii, and iv are true, while ii and v are false.

9. IEEE 829 test plan documentation standard contains all of the following except:

Test items

Test deliverables

Test tasks

Test environment

Test specification

The IEEE 829 test plan documentation standard includes test items, test deliverables, test tasks, and test environment. However, it does not include test specification. Test specification refers to the detailed description of the tests to be executed, including the test inputs, expected outputs, and test conditions. While test specification is an important component of test planning, it is not specifically mentioned in the IEEE 829 standard.

Explanation

The IEEE 829 test plan documentation standard includes test items, test deliverables, test tasks, and test environment. However, it does not include test specification. Test specification refers to the detailed description of the tests to be executed, including the test inputs, expected outputs, and test conditions. While test specification is an important component of test planning, it is not specifically mentioned in the IEEE 829 standard.

10. Which of the following is the main purpose of the integration strategy for integration testing in the small?

To ensure that all of the small modules are tested adequately

To ensure that the system interfaces to other systems and networks

To specify which modules to combine when and how many at once

To ensure that the integration testing can be performed by a small team

To specify how the software should be divided into modules

The main purpose of the integration strategy for integration testing in the small is to specify which modules to combine when and how many at once. This means that the strategy outlines the specific modules that need to be integrated, as well as the timing and quantity of the integration. This ensures that the integration testing process is organized and systematic, allowing for efficient and effective testing of the integrated modules.

Explanation

The main purpose of the integration strategy for integration testing in the small is to specify which modules to combine when and how many at once. This means that the strategy outlines the specific modules that need to be integrated, as well as the timing and quantity of the integration. This ensures that the integration testing process is organized and systematic, allowing for efficient and effective testing of the integrated modules.