From: Junio C Hamano Date: Tue, 31 Jul 2018 20:51:33 GMT Subject: Re: [PATCH 2/8] t3206: add color test for range-diff --dual-color Message-ID: In-Reply-To: <20180731003141.105192-3-sbeller@google.com> Stefan Beller writes: > The 'expect'ed outcome has been taken by running the 'range-diff | decode'. > > Signed-off-by: Stefan Beller > --- > t/t3206-range-diff.sh | 39 +++++++++++++++++++++++++++++++++++++++ > 1 file changed, 39 insertions(+) > > diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh > index 2237c7f4af9..019724e61a0 100755 > --- a/t/t3206-range-diff.sh > +++ b/t/t3206-range-diff.sh > @@ -142,4 +142,43 @@ test_expect_success 'changed message' ' > test_cmp expected actual > ' > > +test_expect_success 'dual-coloring' ' > + cat >expect <<-\EOF && It is a good idea to use something like "sed -e 's/^|//'" instead of "cat" here; that way allows you to mark the left-edge of the data with "|", for a test vector like this one that has a line that would otherwise violate the whitespace style rules. An inferiour alternative would be to add .gitaddtibute entry to make this file exempt from indent-with-tab rule, but even in this 40-line block there only is one line that requires such a workaround, and it won't help the initial application of this patch to get modified when applied with "am --whitespace=fix". > + 1: a4b3333 = 1: f686024 s/5/A/ > + 2: f51d370 ! 2: 4ab067d s/4/A/ > + @@ -2,6 +2,8 @@ > + > + s/4/A/ > + > + + Also a silly comment here! > + + > + diff --git a/file b/file > + --- a/file > + +++ b/file > + 3: 0559556 ! 3: b9cb956 s/11/B/ > + @@ -10,7 +10,7 @@ > + 9 > + 10 > + -11 > + -+BB > + ++B > + 12 > + 13 > + 14 > + 4: d966c5c ! 4: 8add5f1 s/12/B/ > + @@ -8,7 +8,7 @@ > + @@ > + 9 > + 10 > + - BB > + + B > + -12 > + +B > + 13 > + EOF > + git range-diff changed...changed-message --color --dual-color >actual.raw && > + test_decode_color >actual + test_cmp expect actual > +' > + > test_done