IT is a method by which individual units of source code are tested to determine if they are fit for use.

It is the testing of integrated system to evaluate the system's compliance with its specified requirements.

Testing that seeks to uncover software errors by partially retesting a modified program.

None

IT is a method by which individual units of source code are tested to determine if they are fit for use.

It is the testing of integrated system to evaluate the system's compliance with its specified requirements.

Testing that seeks to uncover software errors by partially retesting a modified program.

None

Test Data

Checkpoints

Screenshots of the application under test(AUT)

Object Repository

Synchronisation

Paramerization

Smart identification

Transaction

Object Repository files

VB action files

QTP Action files

Stores test data

Getlinecount

count

Getrowcount

Getcount

Do Loop

Recovery Scenario

IF THEN Statement

Select case statement

Dim Statement

Con Statement

Const Statement

Option Explicit Statement

Analog mode

Low level Recording mode

Normal Recording mode

Run Analog mode

Call Action

Split Action

Reusable Action

Called action

Synchronize

Wait

WaitProperty

Pause

True

False

Is the same as equivalence partitioning tests

Test boundary conditions on, below and above the edges of input and output equivalence classes

Tests combinations of input circumstances

Is used in white box testing strategy

System testing

Usability testing

Performance testing

Both b & c

Data tester

Boundary tester

Capture/Playback

Output comparator

Done by the Developer

Done by the Test Engineers

Done By Management

Done by an Entity Outside the Project’s sphere of influence

updating tests when the software has changed

testing a released system that has been changed

testing by users to ensure that the system meets a business need

testing to maintain business advantage

performed by customers at their own site

performed by customers at the software developer's site

performed by an Independent Test Team

performed as early as possible in the lifecycle

re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects

re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed

re-testing is done after faults are fixed; regression testing is done earlier

re-testing is done by developers; regression testing is done by independent testers

is not important

increases the later a fault is found

decreases the later a fault is found

can never be determined