The credibility of a Database Developer usually ends at the
start of User Testing. Nobody benefits from sloppy testing. A Database
Developer has two options :
 |
Get paid before Testing and flee (my preferred option) |
|
Have a comprehensive test plan, and run through it yourself before exposing the Customer to it. |
If a User to exercises an application, this should not be considered as comprehensive User Testing.
It is a requirement that the Developer allows adequate time for “White Box” testing for every deliverable.
Adequate time should also be allowed for :
|
· Building Test data |
|
· Writing Test Plan and Procedures, if required |
|
· Bug-Fixing following User Testing |
|
· Regression Analysis and Regression Testing |
|
· Conducting Acceptance Data |
|
· Managing Bug and Testing results |
Where User activity is significant, loading, locking and performance should be specifically tested.