On 3/4/2014 12:29 AM, Junio C Hamano wrote:
Ilya Bobyr <ilya.bo...@gmail.com> writes:
While it could be done, it looks less obvious than this:
GIT_TEST_ONLY='1 4' ./t0001-init.sh
If you are thinking about affecting only one test,
Yes, that is the use case: when I am developing a specific feature I
want to run just one test for that feature over and over, while I am
working on that specific thing.
Not the whole test suite (like "t0001"), but just the new case that I've
added to the end, for example. Plus one or more tests that setup enough
environment for it.
shouldn't be mucking with environment variables in the first place,
primarily because running:
$ GIT_TEST_ONLY='1 4' make test
to run test .1 and .4 of all the test scripts would not make any
No it does not. It only makes sense for one test suite.
I think your "simplicity" argument is a total red-herring.
Of course if you do not have to say the test script name, your
specification would be shorter, but that is only because your
specification is not specific enough to be useful.
In my case it is very useful :)
This is why I am saying that we might be talking about different cases:
you are talking about the test suite level, while the issue I am trying
to address an issue at an individual test level.
Giving that as a command line argument to the specific script, e.g.
$ sh ./t0001-init.sh --only='1 4'
might make some sense, but the above GIT_TEST_ONLY does not make any
sense from the UI point of view.
No problem, I guess I can make it look like that - with '--only'.
Maybe '--tests'? Then the same negation syntax could be used as
As well as range syntax.
There are many reasons that makes me unenthused about this line of
change in the first place:
* Both at the philosophical level and at the practical level, I've
found that it always makes sense to run most of the tests, i.e.
skipping ought to be an exception not the norm. Over the course
of this project, I often saw an alleged fix to one part of the
system introduces breakages that are caught by tests that checks
parts of the system that does not have any superficial link to it
(e.g. update the refs code and find a rebase test break).
My main argument is the time. When testing Git as a whole or a feature
as a whole there is no reason to skip some tests.
When working on a specific piece I may run the same test 100 times easily.
Here is what I see on my Cygwin:
$ time ./t0001-init.sh
$ time GIT_SKIP_TESTS='t0001. t0001.??' ./t0001-init.sh
So skipping 34 tests that I am not interested in save a bit more that
50% of the time.
While it would be really nice if it would be faster, this speedup is a
pretty simple one.
* Even though GIT_SKIP_TESTS mechanism still allows you to skip
individual test pieces, it has never been a serious "feature" in
the first place. Many of the tests unfortunately do rely on state
previous sequences of tests left behind, so it is not realistic
to expect that you can skip test pieces randomly and exercise
later test pieces reliably.
* The numbering of individual test pieces can easily change by new
tests inserted in the middle; again, many tests do take advantge
of the states earlier tests leave behind, so "do not add new
tests in the middle" is not a realistic rule to enforce, unless
you are willing to clean up existing test scripts so that each
test piece is independent from all the previous ones.
Both are true, but do not apply to the TDD case.
Neither they apply to a case when a test is broken and I want to execute
everything up to that test.
The latter two makes the ability to skip individual test pieces a
"theoretically it could be made useful but practically not so much"
misfeature. I am very hesitant to see the test framework code
churned only to enhance its "usefulness" when there isn't any in the
first place, without first making changes that fundamentally
improves its usefulness (e.g. to solve "test numbering is not
stable" problem, you could identify the tests with test names
instead of numbers to make it more stable, but that is not what your
patch is even attempting to do).
If you see a way to address my problems, I might be able to code it the
way you want it to be.
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