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

[PATCH v2 00/12] Improve git-pull test coverage

From
Paul Tan <pyokagan@gmail.com>
Date
May 7, 2015, 08:43 UTC
Message-ID
<1430988248-18285-1-git-send-email-pyokagan@gmail.com>
This patch series improves test coverage of git-pull.sh.

This 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.

The previous patch series can be found at [1]. Note that it is now based on jc/merge in pu.

Besides fixing issues raised in the last round, some failing tests have been added to demonstrate some bugs in git-pull.sh, and some tests are modified to reduce their dependence on git-pull's functionality so that irrelevant test suites will not break during the rewrite.

[1] http://thread.gmane.org/gmane.comp.version-control.git/268231
Paul Tan (12):
  t5520: implement tests for 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
  t4013: call git-merge instead of git-pull
  t5520: ensure origin refs are updated
  t7406: use "git pull" instead of "git pull --rebase"
  t5520: failing test for pull --all with no configured upstream
  t5524: test --log=1 limits shortlog length
  t5520: check reflog action in fast-forward merge
 t/t4013-diff-various.sh     |   2 +-
 t/t5520-pull.sh             | 148 +++++++++++++++++++++++++++++++++++++++++++-
 t/t5521-pull-options.sh     |  13 ++++
 t/t5524-pull-msg.sh         |  17 +++++
 t/t7406-submodule-update.sh |   2 +-
 5 files changed, 177 insertions(+), 5 deletions(-)
-- 
2.1.4
Next: Paul Tan
Message 1 of 49 in “Improve git-pull test coverage”
  1. 00/12 Improve git-pull test coveragePaul Tan, May 7, 2015
  2. 01/12 t5520: implement tests for no merge candidates casesPaul Tan, May 7, 2015
  3. Torsten BögershausenMay 7, 2015
  4. Junio C HamanoMay 7, 2015
  5. Paul TanMay 7, 2015
  6. Junio C HamanoMay 7, 2015
  7. Torsten BögershausenMay 7, 2015
  8. 02/12 t5520: test for failure if index has unresolved entriesPaul Tan, May 7, 2015
  9. Eric SunshineMay 7, 2015
  10. Paul TanMay 12, 2015
  11. 03/12 t5520: test work tree fast-forward when fetch updates headPaul Tan, May 7, 2015
  12. Stefan BellerMay 7, 2015
  13. Junio C HamanoMay 7, 2015
  14. Paul TanMay 7, 2015
  15. 04/12 t5520: test --rebase with multiple branchesPaul Tan, May 7, 2015
  16. 05/12 t5520: test --rebase failure on unborn branch with indexPaul Tan, May 7, 2015
  17. Stefan BellerMay 7, 2015
  18. Paul TanMay 7, 2015
  19. Eric SunshineMay 7, 2015
  20. 06/12 t5521: test --dry-run does not make any changesPaul Tan, May 7, 2015
  21. 07/12 t4013: call git-merge instead of git-pullPaul Tan, May 7, 2015
  22. Johannes SchindelinMay 7, 2015
  23. Paul TanMay 7, 2015
  24. Johannes SchindelinMay 8, 2015
  25. Junio C HamanoMay 7, 2015
  26. 08/12 t5520: ensure origin refs are updatedPaul Tan, May 7, 2015
  27. 09/12 t7406: use "git pull" instead of "git pull --rebase"Paul Tan, May 7, 2015
  28. Junio C HamanoMay 7, 2015
  29. Paul TanMay 7, 2015
  30. Junio C HamanoMay 7, 2015
  31. Paul TanMay 10, 2015
  32. 10/12 t5520: failing test for pull --all with no configured upstreamPaul Tan, May 7, 2015
  33. Junio C HamanoMay 7, 2015
  34. Paul TanMay 7, 2015
  35. Junio C HamanoMay 7, 2015
  36. Paul TanMay 9, 2015
  37. 11/12 t5524: test --log=1 limits shortlog lengthPaul Tan, May 7, 2015
  38. Johannes SchindelinMay 7, 2015
  39. Paul TanMay 7, 2015
  40. Johannes SixtMay 7, 2015
  41. Johannes SchindelinMay 8, 2015
  42. Thomas GummererMay 8, 2015
  43. Johannes SchindelinMay 8, 2015
  44. Johannes SixtMay 8, 2015
  45. Junio C HamanoMay 8, 2015
  46. Junio C HamanoMay 7, 2015
  47. 12/12 t5520: check reflog action in fast-forward mergePaul Tan, May 7, 2015
  48. Stefan BellerMay 7, 2015
  49. Junio C HamanoMay 7, 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.