Damaged reputation

Lack of methodology

Inadequate training

Regulatory compliance

Poor quality software

Poor software and poor testing

Bad luck

Insufficient time for testing

Finding defects

Gaining confidence about the level of quality and providing information

Preventing defects

Debugging defects

Prove that the remaining defects will not cause any additional failures

Run all of the tests that are defined for the test object as quickly as possible

Prove that all faults have been identified through thorough testing

Cause as many failures as possible so that faults can be identified and corrected

Determine the productivity of programmers

Eliminate the need for future program maintenance

Eliminate every error prior to release

Uncover software errors

The goal / purpose of testing is to demonstrate that the program works

The purpose of testing is to demonstrate that the program is defect free

The purpose of testing is to demonstrate that the program does what it is supposed to do

Testing is executing Software for the purpose of finding defects

I and II

I and IV

II, IV, and V

III and IV

Developers

Analysts

Testers

Incident Managers

Validation

Testing

Debugging

Verification

Because testing is good method to make there are not defects in the software

Because verification and validation are not enough to get to know the quality of the software

Because testing measures the quality of the software system and helps to increase the quality

Because testing finds more defects than reviews and inspections

Makes test preparation easier

Means inspections are not required

Can prevent fault multiplication

Will find all faults

Phase building activity

Intermediate activity

End of Phase activity

Desing activity

Incorrect program behavior due to a fault in the program

Bug found before product Release

Bug found after product Release

Bug found during Design phase

An error

A fault

A failure

A defect

A mistake

Desviation from expected result to actual result

Defect in the software

Error in the program code

Fault in the system

Creating documentation procedures and allocating resource contingencies

Asking programmers to perform a thorough and independent testing

Combining levels of testing and mandating inspections of all documents

Documenting lessons learned and determining the root cause of problems

Usability defects found by customers

Defects in infrequently used functionality

Defects that were detected early

Minor defects that were found by users

It is cheaper than designing tests during the test phases

It helps prevent defects from being introduced into the code

Tests designed early are more effective than tests designed later

It saves time during the testing phases when testers are busy.

Early testing

Defect clustering

Pesticide paradox

Exhaustive testing

Is not important

Increases as we move the product towards live use

Decreases as we move the product towards live use

Is more expensive if found in requirements than functional design

Can never be determined

i, iii & iv are true. ii & v are false

iii is true, I, ii, iv & v are false

iii & iv are true. i, ii & v are false

i, iii, iv & v are true, ii are false

i & iii are true, ii, iv & v are false

The documentation is poor, so it takes longer to find out what the software is doing.

Wages are rising

The fault has been built into more documentation, code, tests, etc

None of the above

Complete testing of software is attainable if you have enough resources and test tools

With automated testing you can make statements with more confidence about the quality of a product than with manual testing

For a software system, it is not possible, under normal conditions, to test all input and output combinations.

A goal of testing is to show that the software is defect free.

They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.

They are easiest to find during system testing but the most expensive to fix then.

Faults are cheapest to find in the early development phases but the most expensive to fix then.

Although faults are most expensive to find during early development phases, they are cheapest to fix then.

Identifying test conditions only, not Identifying test cases

Not Identifying test conditions, Identifying test cases only

Identifying test conditions and Identifying test cases

Identifying test conditions or Identifying test cases

Test Analysis

Test Design

Test Implementation

Test Closure Activities

Test Implementation

Test execution

Test Analysis

Test Design

Creating test suites from the test cases

Executing test cases either manually or by using test execution tools

Comparing actual results

Designing the Tests

i,ii,iii are true and iv is false

i,iv are true and ii is false

i,ii are true and iii,iv are false

ii,iii,iv are true and i is false

II, III and IV

I, III, IV and V

I, II, III and IV

III, IV and V

We cannot run the test

It may be difficult to repeat the test

It may be difficult to determine if the test has passed or failed

We cannot automate the user inputs

Test Implementation

Test execution

Test Analysis

Test design

Initiating and planning

Documenting root-causes

Capturing lessons learned

Planning and control

Ensuring proper environment setup

Writing a test summary report

Assessing the need for additional tests

Finalizing and archiving testware

i, ii, iv are true and iii is false

i, ii, i are true and iv is false

i, iii, iv are true and ii is false

All of above are true