> -------- Original Message --------
> Subject: test suite in source packages
> From: "Kenneth Porter" <shiva@sewingwitch.com>
> Date: Fri, February 11, 2005 3:27 pm
> To: users@subversion.tigris.org
>
> [quoting whole message now that I've changed the subject line]
>
> [comments in-line; please avoid top-posting, as it makes it difficult to
> keep track of the various subthreads within the discussion.]
>
> --On Friday, February 11, 2005 3:11 PM -0700 scohen@javactivity.org wrote:
>
> > I would suggest two things:
> >
> > 1) I still think it MORE important for the builders of source packages
> > to do this than for the end users. Else what value are the source
> > package builders really providing?
>
> A matter of definition. If the end user is going to use a source package,
> whether it be the original tarball or a derived form like an RPM, he should
> run the test suite to insure that the resulting binary is reliable.
>
> > 2) If it is important for end users to run such tests (to test
> > correctness of configuration) then the error messages should point to
> > problems in the configuration, rather than the developer-centric
> > messages that are emitted now.
> >
> > I think you've just become accustomed to the use of testsuite that is
> > suboptimal because there is nothing better.
>
> I'm sure a patch with better messages would be welcome. User-centric
> messages are best written by users, not developers.
My point is, however, that the current test suite is developer-centric
in design. They are unit tests, designed to enable developers to
regression-test that their changes have not broken previously existing
functionality. As a developer, I love having such a test suite at my
disposal. It's a great tool, enabling me to quickly validate that my
changes do no harm. It was not designed to validate that a user's
system is capable of supporting subversion, which is what it is being
used for in subversion source packages. You want to test that Apache
is working right, and whatever other system components subversion
requires, and that the different components can talk to one another.
If the developers have done their jobs, and as someone who has chosen
to use open source, I trust them, I don't need to run their unit tests,
and frankly, they take longer than I would like. The checks that are
needed are much simpler than this..
>
> >> -------- Original Message --------
> >> Subject: Re: Victory - built subversion from RH9 source rpm!
> >> From: "Jani Averbach" <jaa@jaa.iki.fi>
> >> Date: Fri, February 11, 2005 2:54 pm
> >> To: scohen@javactivity.org
> >> Cc: "Kenneth Porter" <shiva@sewingwitch.com>,
> >> users@subversion.tigris.org
> >>
> >> On 2005-02-11 14:42-0700, scohen@javactivity.org wrote:
> >> > The larger issue, which no one wants to discuss, in spite of my several
> >> > attempts to raise it, is whether the developer unit-test suite is an
> >> > appropriate test suite for inclusion by default in source-build
> >> > packages.
> >> >
> >> Let's talk about it. =)
> >>
> >> I think it is very reasonable thing to do for __source_build__
> >> packages. We have seen several post on dev@ and users@ when something
> >> has went wrong with build or link, and exploded right away with test
> >> suite.
> >>
> >> I have even planned time to time make the test suite a stand-alone
> >> system (which it is quite much, btw), so that you could stress test
> >> your binary installation or current setup with it.
> >>
> >> Of cource this is just IMHO.
> >>
> >> BR, Jani
> >>
> >> --
> >> Jani Averbach
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 23:58:05 2005