To answer this question, you need to understand the concept of software reliability measures and their relationship to testing.

Software reliability measures are used to assess the reliability or stability of a software system. These measures help determine when to stop testing and release the software.

Option A) Exercise system functions in proportion to the frequency they will be used in the released product - This option is the correct answer. When using software reliability measures, it is best to use test cases that mimic the frequency of system functions in the released product. By doing so, you can assess the reliability of the system based on its expected usage patterns.

Option B) Push the system beyond its designed operation limits and are likely to make the system fail - This option is incorrect. While it is important to test the system under stress or extreme conditions, this approach alone may not provide an accurate measure of software reliability. Testing beyond the designed operation limits may not reflect the actual usage of the system and may not provide a reliable indication of its stability.

Option C) Exercise unusual and obscure scenarios that may not have been considered in design - This option is incorrect. While it is important to test for unusual scenarios and edge cases, relying solely on these types of test cases may not provide a comprehensive measure of software reliability. It is best to focus on test cases that reflect the intended usage and frequency of system functions.

Option D) Exercise the most complicated and the most error-prone portions of the system - This option is incorrect. While it is important to thoroughly test complex and error-prone portions of the system, relying solely on these test cases may not provide an accurate measure of software reliability. It is best to consider the overall usage patterns and frequency of system functions when selecting test cases for software reliability measures.

The correct answer is A) Exercise system functions in proportion to the frequency they will be used in the released product. This option is correct because it ensures that the software reliability measures are based on the expected usage patterns and can provide a reliable indication of the system's stability.

• Thanks
• Wrong explanation

To answer this question, let's go through each option:

Option A) Project risks are potential failure areas in the software or system; product risks are risks that surround the project’s capability to deliver its objectives. This option is incorrect. Project risks are not limited to potential failure areas in the software or system, and product risks are not limited to the project's capability to deliver its objectives.

Option B) Project risks are the risks that surround the project’s capability to deliver its objectives; product risks are potential failure areas in the software or system. This option is correct. Project risks refer to the risks that may hinder the project's ability to achieve its objectives, such as delays, budget overruns, or resource constraints. Product risks, on the other hand, are related to potential failure areas in the software or system, such as software bugs or system failures.

Option C) Project risks are typically related to supplier issues, organizational factors, and technical issues; product risks are typically related to skill and staff shortages. This option is incorrect. While project risks can include supplier issues, organizational factors, and technical issues, they are not limited to these factors. Product risks are not typically related to skill and staff shortages.

Option D) Project risks are risks that delivered software will not work; product risks are typically related to supplier issues, organizational factors, and technical issues. This option is incorrect. Project risks are not solely about the delivered software not working, and product risks are not typically related to supplier issues, organizational factors, and technical issues.

The correct answer is B. Project risks are the risks that surround the project’s capability to deliver its objectives, while product risks are potential failure areas in the software or system.

• Thanks
• Wrong explanation

To answer this question, we need to understand the concepts of statement coverage, branch coverage, and decision coverage.

Statement coverage refers to the percentage of statements in the code that have been executed during testing. It measures how many statements have been covered by the test cases.

Branch coverage refers to the percentage of branches in the code that have been executed during testing. It measures how many branches have been covered by the test cases.

Decision coverage refers to the percentage of decision outcomes in the code that have been executed during testing. A decision outcome is a Boolean expression that results in a true or false value. It measures how many decision outcomes have been covered by the test cases.

Now let's go through each statement to determine its correctness:

i. 100% statement coverage guarantees 100% branch coverage. This statement is false. While achieving 100% statement coverage does cover all the branches, it does not guarantee that all the branches have been covered.

ii. 100% branch coverage guarantees 100% statement coverage. This statement is false. Achieving 100% branch coverage means that all the branches have been covered, but it does not guarantee that all the statements have been covered.

iii. 100% branch coverage guarantees 100% decision coverage. This statement is true. Achieving 100% branch coverage ensures that all the decision outcomes have been covered, as each branch represents a decision outcome.

iv. 100% decision coverage guarantees 100% branch coverage. This statement is true. Achieving 100% decision coverage ensures that all the branches have been covered, as each decision outcome corresponds to a branch.

v. 100% statement coverage guarantees 100% decision coverage. This statement is false. Achieving 100% statement coverage does not guarantee that all the decision outcomes have been covered.

Based on the explanations above, the correct answer is:

D. ii, iii & iv are True; i & v are False

• Thanks
• Wrong explanation

To answer this question, let's go through each option to understand why it is correct or incorrect:

Option A) i, iii, iv, v - This option is incorrect because it includes option iii, which is not a disadvantage of capturing tests by recording the actions of a manual tester. Option iii states that expected results must be added to the captured script, which is not a disadvantage but rather a necessary step in creating a test script.

Option B) ii, iv, and v - This option is correct because it includes the correct disadvantages of capturing tests by recording the actions of a manual tester. Option ii states that data for a number of similar tests is automatically stored separately from the script, which can be a disadvantage as it may lead to difficulties in managing and maintaining the test data. Option iv states that the captured script documents the exact inputs entered by the tester, which can be a disadvantage as it may make the script less maintainable and reusable. Option v states that when replaying a captured test, the tester may need to debug the script if it doesn't play correctly, which is a common issue with recorded tests.

Option C) i, ii, and iv - This option is incorrect because it does not include all the correct disadvantages of capturing tests by recording the actions of a manual tester. It is missing option v, which states that the tester may need to debug the script when replaying a captured test.

Option D) i and v - This option is incorrect because it only includes two of the correct disadvantages. It is missing option iv, which states that the captured script documents the exact inputs entered by the tester.

The correct answer is B. This option includes the correct disadvantages of capturing tests by recording the actions of a manual tester: ii, iv, and v.

• Thanks
• Wrong explanation

To answer this question, we need to understand the characteristics of testable software. Let's go through each option to understand why it is correct or incorrect:

Option A) Observability - This option is a characteristic of testable software. Observability refers to the ability to observe and monitor the behavior of the software during testing. It allows testers to gather information about the software's execution, outputs, and internal states.

Option B) Simplicity - This option is not a characteristic of testable software. While simplicity can make software easier to understand and maintain, it does not directly impact its testability.

Option C) Stability - This option is not a characteristic of testable software. Stability refers to the ability of software to remain in a consistent state without crashing or producing unexpected behavior. While stability is desirable in software, it does not directly impact its testability.

Option D) All of the above - This option is the correct answer. Testable software should exhibit all the characteristics mentioned in options A, B, and C. Observability, simplicity, and stability are all important factors that contribute to the testability of software.

Therefore, the correct answer is D) All of the above. This option is correct because all the characteristics mentioned (observability, simplicity, and stability) are important for testable software.

• Thanks
• Wrong explanation

To answer this question, you need to understand different testing techniques. Let's go through each option to understand why it is correct or incorrect:

Option A) Black-box testing - This option is correct because black-box testing is a testing technique that focuses on testing the functionality of a program without considering its internal structure or implementation details. Test cases are devised to demonstrate that each program function is operational, without knowledge of the internal code.

Option B) Glass-box testing - This option is incorrect because glass-box testing, also known as white-box testing, involves testing the internal structure and implementation of a program. It requires knowledge of the internal code and is not focused on demonstrating the operational functionality of each program function.

Option C) Grey-box testing - This option is incorrect because grey-box testing is a combination of black-box and white-box testing techniques. It involves having partial knowledge of the internal code and using that knowledge to design test cases. Grey-box testing does not necessarily focus on demonstrating the operational functionality of each program function.

Option D) White-box testing - This option is incorrect because white-box testing, also known as glass-box testing, involves testing the internal structure and implementation of a program. It requires knowledge of the internal code and is not focused on demonstrating the operational functionality of each program function.

The correct answer is A) Black-box testing. This option is correct because black-box testing is the testing technique that requires devising test cases to demonstrate that each program function is operational, without considering the internal structure or implementation details of the program.

• Thanks
• Wrong explanation

To answer this question, we need to understand the difference between black-box testing and white-box testing.

Black-box testing is a type of testing technique where the internal structure, design, and implementation details of the system under test are not known to the tester. In black-box testing, the tester focuses on testing the functionality of the system without any knowledge of the internal workings of the system. This type of testing is primarily based on requirements and specifications.

White-box testing, on the other hand, is a type of testing technique where the tester has full knowledge of the internal structure, design, and implementation details of the system under test. In white-box testing, the tester can examine the code, data structures, and algorithms to identify potential issues and validate the system against internal behaviors and logic.

Now, let's go through each option to understand which types of errors can be uncovered by white-box testing but missed by black-box testing:

A. Behavioral errors - Black-box testing is focused on testing the behavior of the system based on the input and expected output. It may uncover behavioral errors, so this option is incorrect.

B. Logic errors - White-box testing, with its knowledge of the internal structure and implementation details, can identify logical flaws in the code and algorithms. It can uncover logic errors that may not be detected through black-box testing. This option is correct.

C. Performance errors - Performance errors, such as issues with response time or resource utilization, are typically not related to the internal structure or implementation details. They are more related to the overall system configuration and environment. Both black-box and white-box testing can potentially uncover performance errors. This option is incorrect.

D. Typographical errors - Typographical errors, such as spelling mistakes or syntax errors, are related to the correctness of the code or documentation. White-box testing can uncover typographical errors by examining the code and documentation. Black-box testing may not specifically focus on these types of errors. This option is correct.

Based on the explanations above, we can conclude that option E ("Both b and d") is the correct answer. White-box testing can uncover logic errors (option B) and typographical errors (option D) that may be missed by black-box testing.

• Thanks
• Wrong explanation

To answer this question, we need to understand the concept of cyclomatic complexity.

Cyclomatic complexity is a software metric that measures the complexity of a program by analyzing the number of independent paths through the program's source code. It provides the designer with information about the number of decision points or branches in the program.

Option A) Cycles in the program - This option is incorrect. Cyclomatic complexity is not directly related to cycles in the program. It measures the number of independent paths, not the number of cycles.

Option B) Errors in the program - This option is incorrect. Cyclomatic complexity does not provide information about errors in the program. It is a metric used to measure complexity, not to detect errors.

Option C) Independent logic paths in the program - This option is correct. Cyclomatic complexity measures the number of independent logic paths in the program. It helps the designer understand how complex the program is and identify potential areas of complexity that may require additional testing or refactoring.

Option D) Statements in the program - This option is incorrect. Cyclomatic complexity is not concerned with the number of statements in the program. It focuses on the number of decision points or branches.

Therefore, the correct answer is C) Independent logic paths in the program because cyclomatic complexity provides the designer with information about the number of independent logic paths in the program.

• Thanks
• Wrong explanation