Re: [PATCH] Add verify-all script to run repeated conversions and verify each one

Greg Ward wrote:
> # HG changeset patch
> # User Greg Ward <[email protected]>
> # Date 1250819779 14400
> # Node ID 5f2cf6a14fcce3789fa0b1c5713707a1262c18fc
> # Parent  cf5ad7ec18d51573cfc9347a60fdded88a810c10
> Add verify-all script to run repeated conversions and verify each one.
> Takes a list of CVS repositories to convert+verify on the command
> line, defaulting to most of test-data/*-cvsrepos.

I like the way this is heading, and optimistically see the kernel of a
testing framework that will work with all of the output formats.  But
since the cvs2svn project still doesn't have a "cvs2hg" program, this
script will not be of much use to the non-Greg-Ward members of our
community :-)  So I'll hold off on committing it, unless you need it in
the main repo for some reason.

If this is really going to become a testing framework, then we need to
think about promoting this script and the verify-cvs2svn.py script out
of the "contrib" directory into the maintained part of the project.  At
the same time, we might rename verify-cvs2svn.py to something more
generic and also something importable (i.e., s/-/_/).  Then, also, the
verify-all script could use verify-cvs2svn.py as a Python library rather
than as a separate process.

By the way, to decide what branches and tags need verification, it would
be safer to determine the symbol names from the CVS repo instead of the
target repo.  Otherwise, the verification would not notice if a
conversion forgets a symbol.

In fact, the verification script could input a symbol-info file output
by the main conversion.  This would not only tell it what symbols are
present in the CVS repository, but would also let it know which symbols
were excluded or renamed in the conversion.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2386299

To unsubscribe from this discussion, e-mail: [[email protected]].