will help ensue unchanged areas of the software have not been affected

can only be run during user acceptance testing

will help ensure changed areas of the software have not been affected

will always be automed

Does not meet people needs

Loss of control over reallocation of resources

Cultural difference

Relinquishments of control

2 is a valid reason; 1,3,4&5 are not

1,2,3,4 are valid reasons; 5 is not

1,2,3 are valid reasons; 4&5 are not

All of them are valid

is likely to be fault-free

is unlikely to cause a failure

is likely to be liked by the users

is unlikely to be completed on schedule

After Coding

After external design

After internal design

After freezing the requirements

it may be difficult to repeat the test

It will be difficult to decide if the test has passed or failed

We cannot run the test

We cannot automate the user inputs

Simple Loops

Nested Loops

Concatenated Loops

All of the above

Shorten the time required for testing

Find more faults

Do more effective testing

Do the best testing in the time available

Having good attention to detail

Being diplomatic

Able to be relied on

Able to write software

Deliverable base-lining

Defect prevention

Management reporting

None of the above

Test Factors

Functions/subroutines

All of the above

None of the above

To freeze requirements

To understand user needs

To define the scope of the testing

All of the above

Checking that we are building the right system

Checking that we are building the system right

Performed by an independent test team

Making sure that it is what the user really wants

True

False

True

False

True

False

0,1900,2004,2005

1900, 2004

1899,1900,2004,2005

1899, 1900, 1901,2003,2004,2005

System testing

Usability testing

Performance testing

Both b & c

Data Tester

Boundary Tester

Capture/Playback

Outut Comparator

Statement coverage

Pole Coverage

Condition Coverage

Path Coverage