Paul has one of the larger REALbasic apps out there and probably has
to jump through a lot of hoops (read: workarounds) to get Revolver
working in the best way possible. It wouldn't be the first time
certain things brake after a new release.
This makes me wonder what unit and functional tests REALsoftware is
actually doing to keep things working the way they should. From the
startup sequence of REALbasic, it's clear the application does some
tests.
I'm not saying unit/functional and integration tests should be used
everywhere, but they should at least be used to ensure what's in
there keeps working.
I'm using unit/functional/integration tests in other environments
than REALbasic with great success. Up till now, I've never had any
failures due to refactoring (or even completely rewriting) a class,
as long as my test suite passed.
On 11 Apr 2006, at 16:04, Joseph wrote:
What's wrong with R2? Looks like it has a bunch of fixes.
That said, I agree the fc releases should be public...
~joe
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Paul
Gaspar
Sent: Tuesday, April 11, 2006 9:01 AM
To: REALbasic NUG
Subject: Why no public final candidate?
Hello!
Just a suggestion from me: It is ok if the beta programm is closed,
but why
not publish a public beta or final candidate a week before the
release? Then
RS could prevent unusable releases like r2.
Best regards
Peter De Berdt
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
