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

Re: [PATCH 2/3] t7005: sanitize test environment for subsequent tests

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Aug 11, 2025, 09:59 UTC
Message-ID
<7491b9af-adcd-431a-89e7-ff54708beca6@gmail.com>
In-Reply-To
<144b6ee4-d4b4-4843-841c-93a109e71aa9@gmail.com>
On 10/08/2025 20:44, Phillip Wood wrote:
Show 25 quoted lines
> On 10/08/2025 17:03, D. Ben Knoble wrote:
>>   '
>> -TERM=vt100
>> -export TERM
>> -for i in $vi EDITOR VISUAL core_editor GIT_EDITOR
>> -do
>> -    echo "Edited by $i" >expect
>> -    unset EDITOR VISUAL GIT_EDITOR
>> -    git config --unset-all core.editor
>> -    case "$i" in
>> -    core_editor)
>> -        git config core.editor ./e-core_editor.sh
>> -        ;;
>> -    [A-Z]*)
>> -        eval "$i=./e-$i.sh"
>> -        export $i
>> -        ;;
>> -    esac
>> -    test_expect_success "Using $i" '
>> -        git --exec-path=. commit --amend &&
>> -        git show -s --pretty=oneline >show &&
>> -        <show sed -e "s/^[0-9a-f]* //" >actual &&
>> -        test_cmp expect actual
>> -    '
>> -done

Thinking about it some more, for this test we can put the loop outside of the subshell and test_expect_success so that we don't have to worry about explicitly clearing the variables set from previous iterations.

for i in $vi EDITOR VISUAL core_editor GIT_EDITOR
do
	test_expect_success "Using $i" '
		if test "$1" = core.editor
		then
			test_config core.editor ./e-core_editor.sh
		fi &&
		(
			case "$i" in
			[A-Z]*)
				eval "$i=./e-$i.sh" &&
				export $i
				;;
			esac &&
			PATH="$(pwd):$PATH" \
			    TERM=vt100 git commit --amend &&
		) &&
		test_commit_message HEAD -m "Edited by $i"
	'
done
Thanks
Phillip
Show 98 quoted lines
>> +test_expect_success 'Using individual editors' '
>> +    test_when_finished "test_unconfig --unset-all core.editor" &&
>> +    (
>> +        TERM=vt100 &&
>> +        export TERM &&
>> +        for i in $vi EDITOR VISUAL core_editor GIT_EDITOR
>> +        do
>> +            sane_unset EDITOR VISUAL GIT_EDITOR &&
>> +            test_might_fail git config --unset-all core.editor &&
>> +            echo "Edited by $i" >expect &&
>> +            case "$i" in
>> +            core_editor)
>> +                git config core.editor ./e-core_editor.sh
>> +                ;;
>> +            [A-Z]*)
>> +                eval "$i=./e-$i.sh" &&
>> +                export $i
>> +                ;;
>> +            esac &&
>> +            git --exec-path=. commit --amend &&
> 
> It would be nice to stop abusing --exec-path here and in the next test 
> by adding the current directory to $PATH with
> 
>      PATH="$(pwd):$PATH" git commit --amend
> 
>> +            git show -s --pretty=oneline >show &&
>> +            <show sed -e "s/^[0-9a-f]* //" >actual &&
>> +            test_cmp expect actual
> 
> We need to add "|| return 1" to the last line here and in the test below 
> to reliably error out when test_cmp fails. I'd have thought that our 
> test linting should hove picked this up but maybe it is confused by the 
> subshell.
> 
> Thanks
> 
> Phillip
>> +        done
>> +    )
>> +'
>> -unset EDITOR VISUAL GIT_EDITOR
>> -git config --unset-all core.editor
>> -for i in $vi EDITOR VISUAL core_editor GIT_EDITOR
>> -do
>> -    echo "Edited by $i" >expect
>> -    case "$i" in
>> -    core_editor)
>> -        git config core.editor ./e-core_editor.sh
>> -        ;;
>> -    [A-Z]*)
>> -        eval "$i=./e-$i.sh"
>> -        export $i
>> -        ;;
>> -    esac
>> -    test_expect_success "Using $i (override)" '
>> -        git --exec-path=. commit --amend &&
>> -        git show -s --pretty=oneline >show &&
>> -        <show sed -e "s/^[0-9a-f]* //" >actual &&
>> -        test_cmp expect actual
>> -    '
>> -done
>> +test_expect_success 'Using editors with overrides' '
>> +    (
>> +        TERM=vt100 &&
>> +        export TERM &&
>> +        for i in $vi EDITOR VISUAL core_editor GIT_EDITOR
>> +        do
>> +            echo "Edited by $i" >expect &&
>> +            case "$i" in
>> +            core_editor)
>> +                git config core.editor ./e-core_editor.sh
>> +                ;;
>> +            [A-Z]*)
>> +                eval "$i=./e-$i.sh" &&
>> +                export $i
>> +                ;;
>> +            esac &&
>> +            git --exec-path=. commit --amend &&
>> +            git show -s --pretty=oneline >show &&
>> +            <show sed -e "s/^[0-9a-f]* //" >actual &&
>> +            test_cmp expect actual
>> +        done
>> +    )
>> +'
>>   test_expect_success 'editor with a space' '
>>       echo "echo space >\"\$1\"" >"e space.sh" &&
>> @@ -115,9 +126,8 @@
>>       test_cmp expect actual
>>   '
>> -unset GIT_EDITOR
>>   test_expect_success 'core.editor with a space' '
>> -    git config core.editor \"./e\ space.sh\" &&
>> +    test_config core.editor \"./e\ space.sh\" &&
>>       git commit --amend &&
>>       echo space >expect &&
>>       git show -s --pretty=tformat:%s >actual &&
> 
Previous: Eric SunshineNext: D. Ben Knoble
Message 72 of 73 in “Drop git-exec-path from non-Git child programs”
  1. 0/4 Drop git-exec-path from non-Git child programsD. Ben Knoble, May 20, 2025
  2. 1/4 t7005: sanitize test environment for subsequent testsD. Ben Knoble, May 20, 2025
  3. Patrick SteinhardtMay 21, 2025
  4. D. Ben KnobleMay 21, 2025
  5. 2/4 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, May 20, 2025
  6. Patrick SteinhardtMay 21, 2025
  7. D. Ben KnobleMay 21, 2025
  8. Patrick SteinhardtMay 21, 2025
  9. Junio C HamanoMay 21, 2025
  10. Junio C HamanoMay 21, 2025
  11. 3/4 run-command: prep_childenv on all platformsD. Ben Knoble, May 20, 2025
  12. Patrick SteinhardtMay 21, 2025
  13. Phillip WoodMay 21, 2025
  14. D. Ben KnobleMay 21, 2025
  15. 4/4 drop git_exec_path() from non-Git commands' PATHD. Ben Knoble, May 20, 2025
  16. Junio C HamanoMay 20, 2025
  17. D. Ben KnobleMay 21, 2025
  18. Patrick SteinhardtMay 21, 2025
  19. Phillip WoodMay 21, 2025
  20. Patrick SteinhardtMay 21, 2025
  21. Phillip WoodMay 21, 2025
  22. Patrick SteinhardtMay 26, 2025
  23. Justin ToblerMay 21, 2025
  24. Patrick SteinhardtMay 26, 2025
  25. D. Ben KnobleMay 21, 2025
  26. Junio C HamanoMay 21, 2025
  27. Phillip WoodMay 22, 2025
  28. D. Ben KnobleAug 5, 2025
  29. 0/2 clean up some code around editorsD. Ben Knoble, Aug 5, 2025
  30. Phillip WoodAug 6, 2025
  31. 1/2 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 5, 2025
  32. 2/2 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 5, 2025
  33. 0/3 clean up some code around editorsD. Ben Knoble, Aug 10, 2025
  34. D. Ben KnobleAug 10, 2025
  35. Ben KnobleAug 10, 2025
  36. 0/4 clean up some code around editorsD. Ben Knoble, Aug 11, 2025
  37. Ben KnobleAug 11, 2025
  38. Eric SunshineAug 12, 2025
  39. D. Ben KnobleAug 12, 2025
  40. Junio C HamanoAug 12, 2025
  41. Eric SunshineAug 12, 2025
  42. Junio C HamanoAug 12, 2025
  43. Eric SunshineAug 12, 2025
  44. 0/3 clean up some code around editorsD. Ben Knoble, Aug 12, 2025
  45. Phillip WoodAug 13, 2025
  46. Junio C HamanoAug 13, 2025
  47. D. Ben KnobleAug 13, 2025
  48. 0/3 clean up some code around editorsD. Ben Knoble, Aug 13, 2025
  49. Phillip WoodAug 15, 2025
  50. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 13, 2025
  51. 2/3 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 13, 2025
  52. 3/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 13, 2025
  53. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 12, 2025
  54. 2/3 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 12, 2025
  55. 3/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 12, 2025
  56. 1/4 t7005: use modern test styleD. Ben Knoble, Aug 11, 2025
  57. 2/4 t7005: stop abusing --exec-pathD. Ben Knoble, Aug 11, 2025
  58. 3/4 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 11, 2025
  59. Eric SunshineAug 11, 2025
  60. D. Ben KnobleAug 12, 2025
  61. Eric SunshineAug 12, 2025
  62. 4/4 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 11, 2025
  63. Eric SunshineAug 11, 2025
  64. Junio C HamanoAug 11, 2025
  65. 1/3 t7005: use modern test styleD. Ben Knoble, Aug 10, 2025
  66. Phillip WoodAug 10, 2025
  67. Phillip WoodAug 11, 2025
  68. 2/3 t7005: sanitize test environment for subsequent testsD. Ben Knoble, Aug 10, 2025
  69. Phillip WoodAug 10, 2025
  70. Ben KnobleAug 10, 2025
  71. Eric SunshineAug 10, 2025
  72. Phillip WoodAug 11, 2025
  73. 3/3 editor: use standard strvec API to receive environment for external editorsD. Ben Knoble, Aug 10, 2025

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.