The testing phase is summarized in Table on page .
[IMAGE ]
Table: The Testing Phase
Simply stated, quality is very important.
In many methodologies, the testing phase is a separate phase which is performed after the implementation is completed by a different team. There is merit in this approach because it is hard to see one's own mistakes and a fresh eye can discover obvious errors much faster than the person who has read and re-read the material many times. Unfortunately, by delegating testing to another team this leads to a slack attitude by the implementation team towards quality.
Alternatively, another approach is to delegate testing to the the whole organization. If the teams are to be known as craftsmen, then the teams should be responsible for establishing high quality across all phases. Sometimes, an attitude change must take place to guarantee quality.
Regardless if testing is done after-the-fact or continuously, testing is usually based on a regression technique, split into several major focuses consisting of internal, unit, application, and stress.