Joel Teichroeb <joel@xxxxxxxxxxxxx> writes:
> Ensure the command gives the correct return code
OK. When you know what the correct return code is, we'd prefer to
see it spelled out, i.e.
Ensure that the command succeeds.
Or did you mean that the command outputs nothing?
The test itself looks obviously correct ;-)
> Signed-off-by: Joel Teichroeb <joel@xxxxxxxxxxxxx>
> ---
> t/t3903-stash.sh | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/t/t3903-stash.sh b/t/t3903-stash.sh
> index 3b4bed5c9a..cc923e6335 100755
> --- a/t/t3903-stash.sh
> +++ b/t/t3903-stash.sh
> @@ -444,6 +444,14 @@ test_expect_failure 'stash file to directory' '
> test foo = "$(cat file/file)"
> '
>
> +test_expect_success 'stash create - no changes' '
> + git stash clear &&
> + test_when_finished "git reset --hard HEAD" &&
> + git reset --hard &&
> + git stash create >actual &&
> + test_must_be_empty actual
> +'
> +
> test_expect_success 'stash branch - no stashes on stack, stash-like argument' '
> git stash clear &&
> test_when_finished "git reset --hard HEAD" &&