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

[PATCH v5 7/8] t5521: test --dry-run does not make any changes

From
Paul Tan <pyokagan@gmail.com>
Date
May 29, 2015, 11:44 UTC
Message-ID
<1432899885-25143-8-git-send-email-pyokagan@gmail.com>
In-Reply-To
<1432899885-25143-1-git-send-email-pyokagan@gmail.com>

Test that when --dry-run is provided to git-pull, it does not make any changes, namely:

* --dry-run gets passed to git-fetch, so no FETCH_HEAD will be created
  and no refs will be fetched.
* The index and work tree will not be modified.
Signed-off-by: Paul Tan <pyokagan@gmail.com>
---
 t/t5521-pull-options.sh | 13 +++++++++++++
 1 file changed, 13 insertions(+)
diff --git a/t/t5521-pull-options.sh b/t/t5521-pull-options.sh
index 453aba5..56e7377 100755
--- a/t/t5521-pull-options.sh
+++ b/t/t5521-pull-options.sh
@@ -117,4 +117,17 @@ test_expect_success 'git pull --all' '
 	)
 '
 
+test_expect_success 'git pull --dry-run' '
+	test_when_finished "rm -rf clonedry" &&
+	git init clonedry &&
+	(
+		cd clonedry &&
+		git pull --dry-run ../parent &&
+		test_path_is_missing .git/FETCH_HEAD &&
+		test_path_is_missing .git/refs/heads/master &&
+		test_path_is_missing .git/index &&
+		test_path_is_missing file
+	)
+'
+
 test_done

-- 
2.1.4
Previous: Paul TanNext: Paul Tan
Message 8 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.