Testing

[محروم.كوم]

Here are two suggestions, maybe slightly left field for you guys, but let me run it by you and see how it goes.

1) Test the software before releasing it.

When I say test, I mean alpha test in house for about 3 months then do extensive beta testing to iron out any bugs, fix all of the bugs then issue a release candidate and go through a second round of testing before announcing an official release.

I know its old fashioned, time consuming and worst of all, hard work, but my little software company has had great success with this method for many years as have much larger organisations. It's not fool proof, but it does at least minimise the pain our customers have to go through.

2) Get the current release stable and as bug free as humanly possible before rushing into enhancements. When introducing enhancements, you have to go through the WHOLE of the testing procedure again.


That's all. When upgrading to 4.04 as i have just done, i expect there to be fewer bugs than in the previous version, not more. I expect the ridiculous data base errors to have been sorted; i expect the software to have been extensively tested. We know, for sure, that it hasn't been. Had the software been through a proper beta test you would not have released it in its current state. __DEFINE_LIKE_SHARE__