[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Software Testing Team; Beta testing



PureBytes Links

Trading Reference Links


----- Original Message -----
From: M. Simms <prosys@xxxxxxxxxxxxxxxx>
To: Ivan Figueredo <idf@xxxxxxxxxxxxxx>
Cc: <omega-list@xxxxxxxxxx>
Sent: Monday, November 08, 1999 2:38 PM
Subject: Software Testing Team; Beta testing


> Regarding the message below:
> I was (am) a professional developer, and I know how hard it is to put out
> quality software. But Omega seems to be in dire need of a better Software
> Testing Team than most.
>
> Regards,
>
> Ivan
>
> It's apparent from this and other posts, that OR is not working with the
> right set of users in their beta testing program.

Beta Testing is only a small part into developing bug-free software. In
fact, if you wait to the Beta (or even alpha) test stage, the costs of
fixing bugs are exponential in comparison to what they would be if the
development team set out to implement Best Practice methods. This is a huge
subject in Computer Science, but things like Unit testing (which requires
some form of Component Design/Architechture) is a MINIMUM requirement. The
list gets bigger. In fact, here is a bombshel for you. TS should probably
not have been written in C/C++, UNLESS Omega was willing to make the sources
Open Source so that bugs could be addressed either by the user or possibly
experts on this list.

What would be my language of choice? SmallTalk or CLOS, or even better,
Java - all type-safe languages.

> In fact, I heard it was practically impossible to get INTO the program. I
> have a funny feeling that it is equally hard to GET OUT of it.....meaning
> there is a lot of "dead wood" in their beta test list.
> They are sending out the beta's to "non-users" ?? Perhaps.


Regards,

Ivan