[merge] doc how to use new test features

Martin Pool mbp at sourcefrog.net
Wed May 2 12:50:29 BST 2007

On 5/2/07, Martin Pool <mbp at sourcefrog.net> wrote:
> On 4/27/07, Robert Collins <robertc at robertcollins.net> wrote:

> > > +If a test can't be run, it can say that it's skipped.  This is typically
> > > +used in parameterized tests - for example if a transport doesn't support
> > > +setting permissions, we'll skip the tests that relating to that.  Skipped
> > > +tests are appropriate when there's just no possibility that the test will
> > > +ever run in this situation, and nothing either developers or users can do
> > > +about it.  ::
> >
> > Actually, I disagree with this. Skipping is for things that *can* be
> > fixed. Things that can't be fixed should not show any output as all as
> > its just noise.

Just a bit more on this: so what do you think should happen in the
example I quote here of a transport that can't set permissions?
(Suppose it is one like DAV where (I think) there's just no way we
could add it.)

I feel a bit uncomfortable having it just silently return as if that
feature had been tested.    Even though this is distinguished from
"things we can/should fix" I like seeing that some things weren't run
and why.


More information about the bazaar mailing list