| commit | 5ee4ef8bda516406b0c13df517895321764ad8e4 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Wed, 31 Oct 2018 20:02:00 +0000 (31 13:02 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 2 Nov 2018 02:27:30 +0000 (2 11:27 +0900) | ||
| tree | c57420ab9d11468144a8490eaf268017189ce03f | treesnapshot (tar.gz zip) |
| parent | 6c8fbae619da9ab2066c0d0e74de79f90c998118 | commitdiff |
t3418: decouple test cases from a previous `rebase -p` test case
It is in general a good idea for regression test cases to be as
independent of each other as possible (with the one exception of an
initial `setup` test case, which is only a test case in Git's test suite
because it does not have a notion of a fixture or setup).
This patch addresses one particular instance of this principle being
violated: a few test cases in t3418-rebase-continue.sh depend on a side
effect of a test case that verifies a specific `rebase -p` behavior. The
later test cases should, however, still succeed even if the `rebase -p`
test case is skipped.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
It is in general a good idea for regression test cases to be as
independent of each other as possible (with the one exception of an
initial `setup` test case, which is only a test case in Git's test suite
because it does not have a notion of a fixture or setup).
This patch addresses one particular instance of this principle being
violated: a few test cases in t3418-rebase-continue.sh depend on a side
effect of a test case that verifies a specific `rebase -p` behavior. The
later test cases should, however, still succeed even if the `rebase -p`
test case is skipped.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t3418-rebase-continue.sh | diffblobblamehistory |