Re: Bug testers needed
------=_NextPart_000_0001_01C04D65.123D5960
charset="iso-8859-1"
Thomas, this is a good move in the right direction. The most effective way
of getting bugs out of documents (such as source code), is to have other
people review it. Testing is not the best way to find or remove bugs - it is
a last resort only. If you are serious about producing quality code then
please clean it up first. This will be very useful for yourself and you'll
probably find many bugs before giving it to others. A messy program to
review is just a waste of a lot people's time. In my organisation,
everything to be reviewed must first pass "entry-criteria". This means that
it must, at a casual look by a review leader, meet coding and formatting
standards, be spell-checked, and accompanied by source documents. In the
case of program code, this is a specifications document at a minimum.
Thomas, do you have it written down what your program is trying to achieve?
If you don't, how can anybody know if its working or not? It easy enough to
guess that bugs that crash the program are not meant to be there, but the
bugs that cause other behaviour are often ambiguous. I strongly suggest that
you do these two things before getting other people to spend time looking at
your work.
a) Write down in simple English, everything that the application is trying
to achieve -not how it is achieving these things - but what its meant to
behave like in all circumstances.
b) Make is as tidy and readable as you know how to.
After these have been done, I'd be happy to review your code.
-----
cheers,
Derek Parnell
derekp at solace.com.au
Solace Limited ( http://www.solace.com.au )
Melbourne, Australia
+61 3 9291 7557
|
Not Categorized, Please Help
|
|
