On 3/24/2014 9:58 PM, Junio C Hamano wrote:
> Jeff King <p...@peff.net> writes:
>> On Mon, Mar 24, 2014 at 01:49:44AM -0700, Ilya Bobyr wrote:
>>> Here are some examples of how functionality added by the patch
>>> could be used. In order to run setup tests and then only a
>>> specific test (use case 1) one can do:
>>> $ ./t0000-init.sh --run='1 2 25'
>>> $ ./t0000-init.sh --run='<3 25'
>>> ('<=' is also supported, as well as '>' and '>=').
>> I don't have anything against this in principle, but I suspect it will
>> end up being a big pain to figure out which of the early tests are
>> required to set up the state, and which are not. Having "<" makes
>> specifying it easier, but you still have to read the test script to
>> figure out which tests need to be run.
The idea is that you will use that option when you know what
setup the test need. And the case that I was targeting is when
you are the author of the test, because you are also writing the
relevant functionality or you are really familiar with the test
because you are, again, working on something in that area.
It does not mean you actually have to do it. It is just a
And as you mentioned, "<" helps in another case - when you do not
know enough about the test, but want to run it. For example when
you are just starting with a failed test.
My experience, thought quite limited, is that it is very simple
to understand what the test needs and where it is prepared, if
you are actually adding new test to a test suite. Or if you
spent some time figuring how specific test works. I think this
is mostly because all the tests are rather simple. Which is
definitely a good thing.
This is not for cases when you treat test suites as black boxes.
For example, when you are just checking someone else code.
>> I wonder if it would make sense to "auto-select" tests that match a
>> regex like "set.?up|create"? A while ago, Jonathan made a claim that
>> this would cover most tests that are dependencies of other tests. I did
>> not believe him, but looking into it, I recall that we did seem to have
>> quite a few matching that pattern. If there were a good feature like
>> this that gave us a reason to follow that pattern, I think people might
>> fix the remainder
> This may be worth experimenting with, I would think.
I was also thinking about it a bit. I do not have that much
knowledge on how all the tests are organized. But I did see some
cases where this rule would fail.
One example would be "t\t0000-basic.sh". It could probably be
considered a very special test suite, but if you skip one of
- "test runs if prerequisite is satisfied"
- "unmet prerequisite causes test to be skipped"
the test suite would just exit in the middle. There is a number
of other tests that you do not want to skip for the same reason.
Also, in the same test suite "showing tree with git ls-tree -r"
is a setup test for the next one "git ls-tree -r output for a
known tree". And the same pattern is repeated for some other
I've also looked at "t5601-clone.sh". There is indeed a test
called "setup" at the very beginning. But somewhere in the
middle there is a test called "clone from .git file" that creates
a folder used in two subsequent tests.
In "t0001-init.sh", "re-init on .git file" creates a folder that
is used in the next test called "re-init to update git link".
Maybe these are just some outliers, I do not know for sure.
These were the only test suites I've looked at so far.
I think that if there is a desire to support automatic setup for
tests maybe a rule could be introduced that a test must succeed,
if there is no breakage, if all the tests that match regex
'^(setup|cleanup)\>' before it have been run. It should not be
too complicated to create a target that would automate checking
of this rule.
I am not 100% sure that this kind of change is worth the trouble.
People who run individual tests should probably know why they are
doing it. And as such that might know the prerequisites.
Otherwise I can not come up with a reason to run an individual
On the other hand, the rule may add a bit more structure to the
tests and automated checking could enforce that.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html