Skip to content

G
git

李少辉-开发者 / git
与 Fork 源项目一致

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 05 2月, 2008 4 次提交
  3. 04 2月, 2008 12 次提交
  5. 03 2月, 2008 5 次提交
  7. 02 2月, 2008 4 次提交
    • J
      Sane use of test_expect_failure · 41ac414e
      由 Junio C Hamano 提交于 
      Originally, test_expect_failure was designed to be the opposite
of test_expect_success, but this was a bad decision.  Most tests
run a series of commands that leads to the single command that
needs to be tested, like this:

    test_expect_{success,failure} 'test title' '
	setup1 &&
        setup2 &&
        setup3 &&
        what is to be tested
    '

And expecting a failure exit from the whole sequence misses the
point of writing tests.  Your setup$N that are supposed to
succeed may have failed without even reaching what you are
trying to test.  The only valid use of test_expect_failure is to
check a trivial single command that is expected to fail, which
is a minority in tests of Porcelain-ish commands.

This large-ish patch rewrites all uses of test_expect_failure to
use test_expect_success and rewrites the condition of what is
tested, like this:

    test_expect_success 'test title' '
	setup1 &&
        setup2 &&
        setup3 &&
        ! this command should fail
    '

test_expect_failure is redefined to serve as a reminder that
that test *should* succeed but due to a known breakage in git it
currently does not pass.  So if git-foo command should create a
file 'bar' but you discovered a bug that it doesn't, you can
write a test like this:

    test_expect_failure 'git-foo should create bar' '
        rm -f bar &&
        git foo &&
        test -f bar
    '

This construct acts similar to test_expect_success, but instead
of reporting "ok/FAIL" like test_expect_success does, the
outcome is reported as "FIXED/still broken".
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      41ac414e
    • J
      Update stale documentation links from the main documentation. · 6ce8e44a
      由 Junio C Hamano 提交于 
      This could have been part of the 1.5.4 commit, but it isn't.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      6ce8e44a
    • J
      GIT 1.5.4 · c3c13529
      由 Junio C Hamano 提交于 
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      c3c13529
    • J
      Fix "git checkout -b foo ':/substring'" · 7dc46429
      由 Junio C Hamano 提交于 
      Because ':/substring' extended SHA1 expression cannot take
postfix modifiers such as ^{tree} and ^{commit}, we would need
to do it in multiple steps.  With the patch, you can start a new
branch from a randomly-picked commit whose message has the named
string in it.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      7dc46429
  9. 01 2月, 2008 3 次提交
  11. 31 1月, 2008 5 次提交
  13. 30 1月, 2008 6 次提交
  15. 29 1月, 2008 1 次提交