Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

Re: [PATCH] t9902: protect test from stray build artifacts

From: Jeff King <hidden>
Date: 2016-06-15 22:55:53

Possibly related (same subject, not in this thread)

On Thu, Jan 24, 2013 at 08:19:30PM -0800, Junio C Hamano wrote:
quoted
Ahh, ok, we show one element per line and just make sure "bundle"
is there, and we do not care what other buns appear in the output.
Not so quick, though.  The lower level "read from help -a" is only
run once and its output kept in a two-level cache hierarchy; we need
to reset both.
Ugh, I didn't even think about that.

I wonder if it would be simpler if the completion tests actually ran a
new bash for each test. That would be slower, but it somehow seems
cleaner.
It starts to look a bit too intimately tied to the implementation of
what is being tested for my taste, though.
[...]
+test_expect_success 'help -a read correctly by command list generator' '
+	__git_all_commands= &&
+	__git_porcelain_commands= &&
+	GIT_TESTING_COMMAND_COMPLETION= &&
+	run_completion "git bun" &&
+	grep "^bundle $" out
+'
Agreed. I could take or leave it at this point. It's nice to check that
changes to "help -a" will not break it, but ultimately it feels a bit
too contrived to catch anything useful.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help