This project is mirrored from Updated .
  1. 22 Mar, 2009 1 commit
    • Johannes Sixt's avatar
      Use prerequisite tags to skip tests that depend on symbolic links · 704a3143
      Johannes Sixt authored
      Many tests depend on that symbolic links work.  This introduces a check
      that sets the prerequisite tag SYMLINKS if the file system supports
      symbolic links.  Since so many tests have to check for this prerequisite,
      we do the check in, so that we don't need to repeat the test
      in many scripts.
      To check for 'ln -s' failures, you can use a FAT partition on Linux:
      $ mkdosfs -C git-on-fat 1000000
      $ sudo mount -o loop,uid=j6t,gid=users,shortname=winnt git-on-fat /mnt
      Clone git to /mnt and
      $ GIT_SKIP_TESTS='t0001.1[34] t0010 t1301 t403[34] t4129.[47] t5701.7
                t7701.3 t9100 t9101.26 t9119 t9124.[67] t9200.10 t9600.6' \
              make test
      (These additionally skipped tests depend on POSIX permissions that FAT on
      Linux does not provide.)
      Signed-off-by: default avatarJohannes Sixt <[email protected]>
  2. 13 Jul, 2008 1 commit
  3. 02 Feb, 2008 1 commit
    • Junio C Hamano's avatar
      Sane use of test_expect_failure · 41ac414e
      Junio C Hamano authored
      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: default avatarJunio C Hamano <[email protected]>
  4. 03 Jul, 2007 1 commit
  5. 08 Sep, 2005 1 commit
    • Junio C Hamano's avatar
      Big tool rename. · 215a7ad1
      Junio C Hamano authored
      As promised, this is the "big tool rename" patch.  The primary differences
      since 0.99.6 are:
        (1) git-*-script are no more.  The commands installed do not
            have any such suffix so users do not have to remember if
            something is implemented as a shell script or not.
        (2) Many command names with 'cache' in them are renamed with
            'index' if that is what they mean.
      There are backward compatibility symblic links so that you and
      Porcelains can keep using the old names, but the backward
      compatibility support  is expected to be removed in the near
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
  6. 14 May, 2005 3 commits
    • Petr Baudis's avatar
      Fixed misnamed t/ · 1bb46244
      Petr Baudis authored
      mv t/ t/
    • Petr Baudis's avatar
      Rename some test scripts and describe the naming convention · f50c9f76
      Petr Baudis authored
      First digit: "family", e.g. the absolute basics and global stuff (0),
      the basic db-side commands (read-tree, write-tree, commit-tree), the
      basic working-tree-side commands (checkout-cache, update-cache), the
      other basic commands (ls-files), the diff commands, the pull commands,
      exporting commands, revision tree commands...
      Second digit: the particular command we are testing
      Third digit: (optionally) the particular switch or group of switches
      we are testing
      Freeform part: commandname-details
      Described in the README.
    • Junio C Hamano's avatar
      [PATCH 2/2] The core GIT tests: recent additions and fixes. · 368f99d5
      Junio C Hamano authored
      This set of scripts are designed to test the features and fixes
      we recently added to core GIT.  The convention to call test
      helper function has been changed during the framework cleanup
      (take two), and these tests have been updated to use the cleaned
      up interface.
      Signed-off-by: default avatarJunio C Hamano <[email protected]>
      Note that this does not include the script since it
      tests a patch which was not applied yet.
      Signed-off-by: Petr Baudis's avatarPetr Baudis <[email protected]>