bfile tests

[David Douard-2]

Hi Greg and others,

the repository of your bfile extension does hold symlinks to files not
distributed with the repo, thus making unit tests impossible to run out of a
fresh clone. May you please fix that?

Thanks,
David
--
David Douard                        LOGILAB, Paris (France), [phone]
Formations Python, Zope, Debian :   http://www.logilab.fr/formations
Développement logiciel sur mesure : http://www.logilab.fr/services
Informatique scientifique :         http://www.logilab.fr/science

_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[Greg Ward-17]

On Sat, Oct 31, 2009 at 6:45 AM, David Douard <david.douard@...> wrote:
> the repository of your bfile extension does hold symlinks to files not
> distributed with the repo, thus making unit tests impossible to run out of a
> fresh clone. May you please fix that?

Hmmm, good point.  For those of you not hacking on bfiles, what I've
done is try to use as much of Mercurial's testing infrastructure as I
can without repeating anything.  E.g. the tests are

  tests/test-add
  tests/test-create
  ...

and they are run by

   tests/run-tests.py

which is a symlink to "../../hg-crew/tests/run-tests.py".  That works
fine for me, since I have a clone of hg-crew next to my clone of
hg-bfiles wherever I work on hg-bfiles.

What do other extension developers do to leverage Mercurial's test
infrastructure?  I suppose I could commit a copy of run-tests.py.
Better idea?

Greg
_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[David Douard-2]

On Monday 02 November 2009 15:18:45 Greg Ward wrote:
> On Sat, Oct 31, 2009 at 6:45 AM, David Douard <david.douard@...>
wrote:

> > the repository of your bfile extension does hold symlinks to files not
> > distributed with the repo, thus making unit tests impossible to run out
> > of a fresh clone. May you please fix that?
>
> Hmmm, good point.  For those of you not hacking on bfiles, what I've
> done is try to use as much of Mercurial's testing infrastructure as I
> can without repeating anything.  E.g. the tests are
>
>   tests/test-add
>   tests/test-create
>   ...
>
> and they are run by
>
>    tests/run-tests.py
>
> which is a symlink to "../../hg-crew/tests/run-tests.py".  That works
> fine for me, since I have a clone of hg-crew next to my clone of
> hg-bfiles wherever I work on hg-bfiles.
>
> What do other extension developers do to leverage Mercurial's test
> infrastructure?  I suppose I could commit a copy of run-tests.py.
> Better idea?

Just write this in a README file in the tests directory :-)


> Greg
> _______________________________________________
> Mercurial mailing list
> Mercurial@...
> http://selenic.com/mailman/listinfo/mercurial



--
David Douard                        LOGILAB, Paris (France), [phone]
Formations Python, Numpy, Debian :  http://www.logilab.fr/formations
Développement logiciel sur mesure : http://www.logilab.fr/services
Informatique scientifique :         http://www.logilab.fr/science

_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial

[Martin Geisler-4]

Greg Ward <greg-hg@...> writes:

> What do other extension developers do to leverage Mercurial's test
> infrastructure?  I suppose I could commit a copy of run-tests.py.

I haven't found a better way than committing run-tests.py. I've done
this for the hg-eol extension:

  http://bitbucket.org/mg/hg-eol/src/

It only works when you use the Makefile, it takes care to add --with-hg
to run-tests.py so that it uses the hg in your PATH.

I got this from the histedit extension:

  http://bitbucket.org/durin42/histedit/src/

So now we can start a trend :-)

--
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.


_______________________________________________
Mercurial mailing list
Mercurial@...
http://selenic.com/mailman/listinfo/mercurial