Ans: The test suite which exercises the functionality of product but doesn’t concentrate on testing all features in detail.

Ans: This is a testing technique used to satisfy coverage criteria which require that each decision point and each coverage point is executed at least once.

Ans: Boundary value analysis is selection of technique in which test data are selected to lie on boundaries of input domain, procedures and parameters. This is similar to equivalence partioning but focus on corner cases or values that are usually out of range as defined by specification.

Ans: This is an inaccurate step, process or data definition in a computer program which causes the program to run in an unintended or unanticipated manner.

Ans: Bug is a fault in program which causes the program to perform in an inadvertent or unanticipated manner.

Ans: This testing mainly focuses on the circumference or limit conditions of the software that is being tested. (Some of these tests are even called as stress tests)

Ans: This is an approach to integration testing where the low level requirements are first tested and then used to assist testing of higher level components. This process continues until the components at top of hierarchy are tested.

What is black box testing?

Ans: This test is based on an analysis of the specification of software without reference to its internal working. The main goal of testing is to test how well the component match to publish requirements for the component.

Ans: This testing is used for executable application to check portability across system platforms and environments.

Ans: Beta testing comes after alpha testing and can be considered as a form of external user acceptance testing. The software is sent to certain group of potential customers who use it in a live environment.