Re-testing is running a test again; regression testing looks for unexpected side effects

Re-testing is done by developers, regression testing is done by independent testers

Re-testing looks for unexpected side effects; regression testing is repeating those tests

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

Re-testing uses different environments, regression testing uses the same environment

The easiest tests first (to give initial confidence)

The order they are thought of

The most important tests first

The most difficult tests first (to allow maximum time for fixing)

Will always be automated

Will help ensure 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

Metrics from previous similar projects

Time allocated for regression testing

Discussions with the development team

Metrics from previous similar projects and discussions with the development team

When the software requirements have been approved

When the design is complete

When the first code module is ready for unit testing

When the code is complete

Test whatever is easiest to test

Test high risk areas

Find as many faults as possible

Obtain good test coverage

Supplements formal test design techniques

Is only performed in user acceptance testing

Can only be used in component, integration and system testing

Is not repeatable and should not be used