Early test analysis and design.
Different test levels are defined with specific objectives.
Testers will start to get involved as soon as coding is done.
A and B above.
Objectives should be generic for any test level.
Objectives are the same for each test level.
The objectives of a test level don't need to be defined in advance.
Each level has objectives specific to that level.
Measuring response time on an on-line booking system.
Checking the effect of high volumes of traffic in a call-center system.
Checking the on-line bookings screen information and the database contents against the information on the letter to the customers.
Checking how easy the system is to use.
There is no time to test the change before it goes live, so only the best developers should do this work and should not involve testers as they slow down the process.
Just run the retest of the defect actually fixed.
Always run a full regression test of the whole system in case other parts of the system have been adversely affected.
Retest the changed area and then use risk assessment to decide on a reasonable subset of the whole regression test to run in case other parts of the system have been adversely affected.
Is only run once.
Will always be automated.
Will check unchanged areas of the software to see if they have been affected.
Will check changed areas of the software to see if they have been affected.
Testing to see where the system does not function correctly.
Testing the quality attributes of the system including reliability and usability.
Gaining user approval for the system.
Testing a system feature using only the software required for that function.
Performed by customers at their own site
Performed by customers at their software developer’s site
Performed by an independent test team
Useful to test bespoke software or Useful to test software developed for a specific customer or user.