Unit |
Traditionally done by developers when modules/units of code are developed Testing is done at the end of an assigned unit of work(coding) Developer completes to confirm- "have i finished this task?"-exitcriteria |
Integration |
Testing done at the time when the work of one or more task assignments are conbined, thus the term integration Stubs are included for missing elements of the system |
System |
The entire system has been integrated together Completed functional testing implemented Development team focuses on correcting defects identified in testing process Note: The development team must believe here that if system testing passes the product will go to the field. |
Acceptance |
Customer runs his/her own testing to confirm that the system meets marketingg requirements Generally acceptance testing plan has been known by system testing tesm. |
Live | Non-intrusive testing of the system while it is in use to measure quality factors such as performance, system resource use, and to spot check correct operation. |
NOTE:
Acceptance testing: Usually ends up with money changing hands, The owners of the contract verify that the application behaves as they intended in the contract. Usually the acceptance tests are written before the application is developed.
Live Testing: Similar to Beta testing