Kyle, > In order to progressively test a product, a base line of > functionality has to be established with a completely functional > stable product. Then as each each feature is implemented, it's > fuctionality is tested. If it breaks a stable function, that is > fixed before anything else is implemented in order to update a stable base.
The unhappy truth of programming is that functions are interrelated in ways that often baffle non-programmers. Is it necessary for a working function to no longer work simply because some change has been made? Such things do often happen. So there is a testing strategy called regression testing. With every new alpha (which is not even good enough to be called a beta, so pretty shaky), testers go through the entire program looking for things that don't work any more. Yes, absolutely report these, but understand that fixing those things will have whatever priority the necessities of programming reality dictate. It might be necessary to put that issue on hold for a while and look at other things. It might be that the resolution of the problem will depend on what happens with those other things, for instance. >Agan, It is not my intent to be insulting or say I can do it better. I am just >trying to >determine if I should continue using TB on a daily basis as my client or move >to >something more stable and watch for a notice that TB has has been released. The "You are about to use an alpha version" message when TB starts is serious and fair warning. You should heed it and accept or reject the risk as your needs dictate. -- Gleason Using 4.0.0.17 (ALPHA) on Windows XP, 5.1, Build 2600. IMAP email provider is Fastmail, which uses Cyrus server software. ________________________________________________________ Current beta is 4.0.0.16 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
