From: Junio C Hamano <gitster@pobox.com>
To: "Ray Chuan" <rctay89@gmail.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH 3/3] http-push: update tests
Date: Sat, 17 Jan 2009 10:54:50 -0800 [thread overview]
Message-ID: <7vsknh7og5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <be6fef0d0901170040r7e11806et87cc5dc3c6f13a2a@mail.gmail.com> (Ray Chuan's message of "Sat, 17 Jan 2009 16:40:38 +0800")
"Ray Chuan" <rctay89@gmail.com> writes:
>>> -test_expect_failure 'push to remote repository' '
>>> +test_expect_success 'push to remote repository' '
>>> cd "$ROOT_PATH"/test_repo_clone &&
>>> : >path2 &&
>>> git add path2 &&
>>> test_tick &&
>>> git commit -m path2 &&
>>> - git push &&
>>> - [ -f "$HTTPD_DOCUMENT_ROOT_PATH/test_repo.git/refs/heads/master" ]
>>> + git push origin master
>>> '
>>
>> ... this removal? I do not think this is a good change, as it removes
>> a test that is actually pretty important.
>
> i'm sorry for the poor commit message, what i wanted to do was to
> change the tests to expect success rather than failure. no tests were
> removed; only their expected outcomes were modified. currently, the
> pushes fail, so the test 'fails as expected'; now the pushes succeed,
> so they shouldn't be expecting failed pushes (or anything else).
The original seems to want the push to succeed, and also it wants the file
refs/heads/master to be present after the push (presumably because there
should be that ref when the push succeeds). If you fixed "push" that used
to fail to succeed, that is great, and s/failure/success/ is a good thing.
But you are removing something else without explanation. Why do you need
to remove the part of the test that checks if refs/heads/master is present?
Is it looking for a file in a wrong place?
next prev parent reply other threads:[~2009-01-17 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 2:59 [PATCH 3/3] http-push: update tests Ray Chuan
2009-01-17 5:23 ` Johannes Schindelin
2009-01-17 8:40 ` Ray Chuan
2009-01-17 18:54 ` Junio C Hamano [this message]
2009-01-17 19:37 ` Johannes Schindelin
2009-01-17 19:55 ` Ray Chuan
2009-01-17 20:21 ` Jakub Narebski
2009-01-17 21:00 ` Ray Chuan
2009-01-17 21:15 ` Jakub Narebski
2009-01-17 21:24 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vsknh7og5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).