On 7/29/05, Liz <[EMAIL PROTECTED]> wrote: > We've seen a lot of releases where strange odd things are broken, and > it seems that a lot of unit tests usually done by the developer are > either skipped or somehow successful where for so many of us it fails.
With that said, I'm quite certain that regression testing in non-existent. Well, precluding this list ;-) > As a developer I do know how hard it is to write something to suit > everyone, however, if you broke something that used to work, rather > than add new stuff, its much better for the confidence of your > userbase to fix the broke stuff, before adding new. We all understand > breakages, stuff happens, but when it remains broken, and ignored.. > quite often people report bugs because they used that feature, and > now their usage is hampered. Another concern of mine is the actual development strategy. Now, I know agile and XP methods are the new fad in development and are not suitable for everything, but it would benefit RL to adopt some of these practices. For example, saying the next beta series is going to address IMAP is unreasonable. IMAP is a big component and it's currently broken in a lot of ways. If instead RL broke things down into user stories, e.g., "The user clicks the delete button and the message is removed immediately" and worked on getting some of those accomplished in short, iterative cycles, they'd probably see much better results. As it is, when we see things such as IMAP fixes, the fixes are so disjoint from one another that it's not even clear what the focus was. Now, feel free to replace IMAP with any particular feature you'd like to see working. -- Kevin ________________________________________________________ Current beta is 3.5.33 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
