git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v5 0/8] Improve git-pull test coverage

From
Paul Tan <pyokagan@gmail.com>
Date
May 29, 2015, 11:44 UTC
Message-ID
<1432899885-25143-1-git-send-email-pyokagan@gmail.com>
This is a re-roll of [1].

This patch series improves test coverage of git-pull.sh, and is part of my GSoC project to rewrite git-pull into a builtin. Improving test coverage helps to prevent regressions that could occur due to the rewrite.

Thanks Junio, Johannes and Stefan for the reviews last round.
[1] http://thread.gmane.org/gmane.comp.version-control.git/269236
Paul Tan (8):
  t5520: prevent field splitting in content comparisons
  t5520: test no merge candidates cases
  t5520: test for failure if index has unresolved entries
  t5520: test work tree fast-forward when fetch updates head
  t5520: test --rebase with multiple branches
  t5520: test --rebase failure on unborn branch with index
  t5521: test --dry-run does not make any changes
  t5520: check reflog action in fast-forward merge
 t/t5520-pull.sh         | 198 +++++++++++++++++++++++++++++++++++++++---------
 t/t5521-pull-options.sh |  13 ++++
 2 files changed, 175 insertions(+), 36 deletions(-)
-- 
2.1.4
Next: Paul Tan
Message 1 of 10 in “Improve git-pull test coverage”
  1. 0/8 Improve git-pull test coveragePaul Tan, May 29, 2015
  2. 1/8 t5520: prevent field splitting in content comparisonsPaul Tan, May 29, 2015
  3. 2/8 t5520: test no merge candidates casesPaul Tan, May 29, 2015
  4. 3/8 t5520: test for failure if index has unresolved entriesPaul Tan, May 29, 2015
  5. 4/8 t5520: test work tree fast-forward when fetch updates headPaul Tan, May 29, 2015
  6. 5/8 t5520: test --rebase with multiple branchesPaul Tan, May 29, 2015
  7. 6/8 t5520: test --rebase failure on unborn branch with indexPaul Tan, May 29, 2015
  8. 7/8 t5521: test --dry-run does not make any changesPaul Tan, May 29, 2015
  9. 8/8 t5520: check reflog action in fast-forward mergePaul Tan, May 29, 2015
  10. Junio C HamanoMay 29, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.