Andy Bradford wrote:
>
> I guess these tests are failing because file1.test didn't setup a test
> repository for their tests?
>
I think so. I think the additional procedures required to do all the fancy
test isolation were added after that test file.
It would be nice if the tests were all c
Thus said "Joe Mistachkin" on Wed, 29 Jul 2015 20:01:33 -0700:
> Another good (and recent) example test file is "mv-rm.test", which
> shows how to setup and start munging a dedicated test repository
> during the tests.
Thanks, I'll have a look at that.
I guess these tests are failing
Andy Bradford wrote:
>
> However, when I run it this way, some of the tests fail because they
> want to be in an open checkout of a repository; specifically the
> relative-tree-name and absolute-tree-name tests from file1.test.
>
Normally, when developing a new feature, I add a test
Hello,
To be able to add tests for the new command I've been familiarizing
myself with tester.tcl and the tests. The instructions for using it say:
From a private directory (not the source tree) run "tclsh
$SRC/test/tester.tcl $FOSSIL" where $FOSSIL is the name of the
ex
