Black Box, White Box, Grey Box MCQ Quiz in বাংলা - Objective Question with Answer for Black Box, White Box, Grey Box - বিনামূল্যে ডাউনলোড করুন [PDF]

Performance testing is designed to test the run-time performance of software within the context of an integrated system. Performance testing occurs throughout all steps in the testing process.

Performance tests are often coupled with stress testing and usually require both hardware and software instrumentation.

Stress testing executes a system in a manner that demands resources in abnormal quantity, frequency, or volume.

For example,

(1) special tests may be designed that generate ten interrupts per second, when one or two is the average rate

(2) input data rates may be increased by an order of magnitude to determine how input functions will respond

(3) test cases that require maximum memory or other resources are executed

(4) test cases that may cause thrashing in a virtual operating system are designed

(5) test cases that may cause excessive hunting for disk-resident data are created. Essentially, the tester attempts to break the program

The alpha test is conducted at the developer's site by a customer. Alpha tests are conducted in a controlled environment.

The beta test is conducted at one or more customer sites by the end-user of the software. Unlike alpha testing, the developer is generally not present. Therefore, the beta test is a "live" application of the software in an environment that cannot be controlled by the developer.

Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.

Once source code has been generated, software must be tested to uncover as many errors as possible before delivery to the customer.
Reviews and other SQA activities can and do uncover errors, but they are not sufficient. Hence, there is a need to execute the program before it gets to the customer with the specific intent of finding and removing all errors.

In desk-checking programmer mentally trace, or check, the logic of the program to attempt to ensure that it is error-free and workable.

Many organizations take this phase a step further with a walkthrough, a process in which a group of programmers review the program and offer suggestions in a collegial way.

• A software product is normally tested in three levels or stages: Unit testing, Integration testing and System testing
• During unit testing, the individual functions (or units) of a program are tested
• After testing all the units individually, the units are slowly integrated and tested after each step of integration (integration testing)
• Finally, the fully integrated system is tested (system testing)
• Integration and system testing are known as testing in the large

Statement P:

A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.

This statement is correct. Statement coverage means executing each statement at least once. Whereas Path coverage is in which every distinct entry – exit path through the code is executed at least once in some test. It is a white box technique. It tells about how well the source code has been made. A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.

Statement Q:  

A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage

Sometimes, during minimal test it can be the possibility that test suite produce 100% statement coverage will miss certain defects related to control structure. So, this statement is correct.

Statement R: A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage

Branch coverage means, for each branch is chosen at least once in some test. It includes statement coverage. As, in case of statement coverage, test suite sometimes cannot detect all faults. So, this statement is not correct that a minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.

• A software product is normally tested in three levels or stages: Unit testing, Integration testing and System testing
• During unit testing, the individual functions (or units) of a program are tested
• After testing all the units individually, the units are slowly integrated and tested after each step of integration (integration testing)
• Finally, the fully integrated system is tested (system testing)
• Unit testing is referred to as testing in the small, whereas integration and system testing are referred to as testing in the large

• Verification and validation techniques are very similar since both these techniques are designed to help remove errors in a software
• In spite of the apparent similarity between their objectives, the underlying principles of these two bug detection techniques and their applicability are very different
• Verification is the process of determining whether the output of one phase of software development conforms to that of its previous phase
• Validation is the process of determining whether a fully developed software conforms to its requirements specification

• A failure of a program essentially denotes an incorrect behavior exhibited by the program during its execution
• An incorrect behavior is observed either as an incorrect result produced or as an inappropriate activity carried out by the program; Every failure is caused by some bugs present in the program
• In other words, we can say that every software failure can be traced to some bug or other present in the code

Tips and Tricks:

It may be noted that mere presence of an error in a program code may not necessarily lead to a failure during its execution.