If you are writing a little web page for you and your friends to use, then your friends don't mind helping you "debug" your web app. However, if you are looking at distributing the web-application, then a formalized process is always good. For large corporations, they of course have whole teams devoted to testing, And you are supposed to send as much time testing as you spend developing.
I will also add my voice to those saying that having someone external to your project test the application. Being intertwined with the app, you are biased as to what the app can and cannot do. Usually an outside source will try something which will have never occurred to you (like press the back button... ;)
Good Process:
Implement Feature
Test Feature
When you have a solid set of Implemented features:
Create Formal "Build"
Ensure basic functionality in Build Works
(Automated Build Verification / Platform / Regression Tests)
Retest all Features implemented in this build.
Have someone else test the build.
Of course, actually using our own product is also always a good thing. When you use it in real life situations, things always come up that may be good features for future releases.
This, of course, is from a Developers POV, and we invariably miss something. So I now submit this to the board for QA... ;)
|
