Did we decide on Perl or Python? :-)
I'll reiterate my position of trying to stick with /bin/sh and awk. Those
two tools are quite portable. Worst case, maybe a .BAT file for Windows in
place of the /bin/sh. But the awk scripts are definitely easy, portable, and
devoid of religious fervor :-)
If awk is disagreeable, then I'd recommend a small Perl harness (it is more
suitable to spawning subprocesses, piping, and filtering than Python).
Cheers,
-g
p.s. yes, I know... I'd love to use Python, but Python's strengths show in
developing programs, rather than as an I/O harness
On Mon, Mar 26, 2001 at 11:02:15PM -0000, kfogel@tigris.org wrote:
> User: kfogel
> Date: 01/03/26 15:02:15
>
> Added: subversion/tests/clients/cmdline README common.sh
> Log:
> Starting automated cmdline client test system. This may or may not be
> the final form of this test system, but we need something right now,
> because the cmdline client functionality has long since ballooned to
> the point of needing automated tests.
>
> Revision Changes Path
> 1.1 subversion/subversion/tests/clients/cmdline/README
>
> Index: README
> ===================================================================
> Test suite for the command line client.
> =======================================
>
> Currently, the command line client lives in ../../../client/, for
> historical reasons, and is the only testable Subversion client.
> Eventually, though, it will live in ../../../clients/cmdline/, and be
> one of many clients; that's why the test dir is tests/clients/cmdline/
> instead of tests/client/.
>
> The cmdline client test suite doesn't use the C-level testing
> framework. Instead, it drives the client just like a user would,
> examining the output and the on-disk results (i.e., the working copy)
> carefully as it goes.
>
>
>
> 1.1 subversion/subversion/tests/clients/cmdline/common.sh
>
> Index: common.sh
> ===================================================================
> #!/bin/sh
>
> SVN_PROG=../../../client/svn
> XML_DIR=../../xml
> TEST_WC_PREFIX="test-wc"
> COMMIT_RESULTFILE_NAME=commit
>
> check_status()
> {
> res=$?
> if [ $res -ne 0 ]; then
> echo Oops, problem: ${@-"(no further details)"}
> exit $res
> fi
> }
>
>
>
--
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006