[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-core-dev] running the tests before releasing
|
You might want to consider something like Cruise Control in the future. From experience I know that doing a significant amount of tests before releasing code reduces productivity. CC gets the tests run soon after the push so a problem can be detected and fixed quickly but doesn't burden the developer in the 99% of the time that the tests won't find anything wrong.
> -----Original Message-----
> From: DJ Houghton
> Sent: Friday, May 28, 2004 8:50 AM
>
> This is a reminder to please run all the tests before
> releasing code to
> HEAD. In the past couple of days code has been released which
> has surfaced
> (easily reproducable) errors in downstream test suites. I
> realize that it
> is unreasonable to ask that all the tests be run for all
> components, but we
> should be running the OSGi, Runtime, and Resources tests.
>
> We're getting closer to the release and the integration
> builds should not
> be used as a method of testing our code...any code that we
> submit we need
> to be confident that it doesn't break anything. And the
> earlier that we
> find bugs in our code so we can fix them, the better.
>
> Thanks.
>
