Re: How to build an expected_status to check against unversioned items?

Rui, Guo wrote:
> Hi all,
>
> I'm writing a test cases for the situation of folding sub-trees that contain
> unversioned/modified items. I'm wondering which flag to use when constructing
> the expected_status (a.k.a. the status_tree). A '? ' does not work because the
> command line (svn st -v -u -q) used to generate actual status tree in the test
> framework will not include unversioned items at all.

There's a function 'run_and_verify_unquiet_status' that will include the
unversioned items in the actual status tree. There's only test that uses
it and it's not really a good example.

In your case, where the point of the test is to get unversioned items I
propose you use this function.

> Should I exclude unversioned items from the status_tree and rely on the
> disk_tree to check against them? Does this way accurate enough?

I think we normally do this though, as for most of the tests unversioned
files are only side effects, like conflict files in update/merge.

hth,

Lieven

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-17 19:10:59 CEST