It is a repository for storing versioned project artifacts and metadata

It is the creation of multiple releases of a product that's improved, upgraded or customized

It is the management of changes of computer files

It is a component of a program that knows how to perform certain actions

Acceptance testing performed by the customer at the Tester's site

Acceptance testing performed by the customer at the developer's site

Acceptance testing performed by the customer in Live environment

Acceptance testing performed by the customer in client environment

Feature pointa

External reference files

Function points

Internal Interface files

True

False

AIX

HP UNIX

Solaris

MS DOS

Linux

True

False

Performance and Functionality

Functionality and usability

Usability and Performance

None of the above

Linguistic Testing

Localization Testing

Both A and B

None of the above.

Several levels of component that includes objects and classes

Several levels of component that includes objects, classes, systems

Several levels of component that includes, foundation components, systems

None of the above.

Combination of one or more testing techniques

Combination of top-down and bottom-up testing

Both A and B

None of the above.

Creating additional test cases to increase coverage

Finding areas of program exercised by the test cases

Determining a quantitative measure of code coverage, which is a direct measure of quality.

All of the above.

Same as glass box testing

Same as clear box testing

Both A and B

None of the above.

Similar to proof reading

Widely used in web testing

Part of usability Testing

All of the above

Testing the boolean expressions which are not in control structures

Entire expression is considered as boolean expression irrespective of logical-and and logical-or operators

Coverage except switch-statement cases, exception handlers

All of the above.

Require a driver to test

No need of instances of other classes

No need to test the transitions

All of the above.

Same as smoke test

Done after each build to make sure that the build doesn’t contain major errors

Both A and B

None of the above.

To find whether the hardware burns out

Same as build verification test

To find that software is stable

None of the above

A type of dynamic testing

Type of static testing

Neither dynamic nor static

Performed by the testing team

Same as static testing

Done by the developers

Both A and B

None of the above

Focused Testing, Testing coverage, control flow

Data integrity, Internal boundaries, algorithm specific testing

Both A and B

Either A or B