Andrew's git - gitweb.git/blob

   1#!/bin/sh
   2#
   3# Copyright (c) 2005 Junio C Hamano
   4#
   5
   6test_description='Test the very basics part #1.
   7
   8The rest of the test suite does not check the basic operation of git
   9plumbing commands to work very carefully.  Their job is to concentrate
  10on tricky features that caused bugs in the past to detect regression.
  11
  12This test runs very basic features, like registering things in cache,
  13writing tree, etc.
  14
  15Note that this test *deliberately* hard-codes many expected object
  16IDs.  When object ID computation changes, like in the previous case of
  17swapping compression and hashing order, the person who is making the
  18modification *should* take notice and update the test vectors here.
  19'
  20. ./test-lib.sh
  21
  22################################################################
  23# init-db has been done in an empty repository.
  24# make sure it is empty.
  25
  26find .git/objects -type f -print >should-be-empty
  27test_expect_success \
  28    '.git/objects should be empty after git-init-db in an empty repo.' \
  29    'cmp -s /dev/null should-be-empty' 
  30
  31# also it should have 257 subdirectories.  258 is counting "objects"
  32find .git/objects -type d -print >full-of-directories
  33test_expect_success \
  34    '.git/objects should have 257 subdirectories.' \
  35    'test $(wc -l < full-of-directories) = 258'
  36
  37################################################################
  38# Basics of the basics
  39
  40# updating a new file without --add should fail.
  41test_expect_failure \
  42    'git-update-cache without --add should fail adding.' \
  43    'git-update-cache should-be-empty'
  44
  45# and with --add it should succeed, even if it is empty (it used to fail).
  46test_expect_success \
  47    'git-update-cache with --add should succeed.' \
  48    'git-update-cache --add should-be-empty'
  49
  50test_expect_success \
  51    'writing tree out with git-write-tree' \
  52    'tree=$(git-write-tree)'
  53
  54# we know the shape and contents of the tree and know the object ID for it.
  55test_expect_success \
  56    'validate object ID of a known tree.' \
  57    'test "$tree" = 7bb943559a305bdd6bdee2cef6e5df2413c3d30a'
  58
  59# Removing paths.
  60rm -f should-be-empty full-of-directories
  61test_expect_failure \
  62    'git-update-cache without --remove should fail removing.' \
  63    'git-update-cache should-be-empty'
  64
  65test_expect_success \
  66    'git-update-cache with --remove should be able to remove.' \
  67    'git-update-cache --remove should-be-empty'
  68
  69# Empty tree can be written with recent write-tree.
  70test_expect_success \
  71    'git-write-tree should be able to write an empty tree.' \
  72    'tree=$(git-write-tree)'
  73
  74test_expect_success \
  75    'validate object ID of a known tree.' \
  76    'test "$tree" = 4b825dc642cb6eb9a060e54bf8d69288fbee4904'
  77
  78# Various types of objects
  79mkdir path2 path3 path3/subp3
  80for p in path0 path2/file2 path3/file3 path3/subp3/file3
  81do
  82    echo "hello $p" >$p
  83    ln -s "hello $p" ${p}sym
  84done
  85test_expect_success \
  86    'adding various types of objects with git-update-cache --add.' \
  87    'find path* ! -type d -print0 | xargs -0 git-update-cache --add'
  88
  89# Show them and see that matches what we expect.
  90test_expect_success \
  91    'showing stage with git-ls-files --stage' \
  92    'git-ls-files --stage >current'
  93
  94cat >expected <<\EOF
  95100644 f87290f8eb2cbbea7857214459a0739927eab154 0       path0
  96120000 15a98433ae33114b085f3eb3bb03b832b3180a01 0       path0sym
  97100644 3feff949ed00a62d9f7af97c15cd8a30595e7ac7 0       path2/file2
  98120000 d8ce161addc5173867a3c3c730924388daedbc38 0       path2/file2sym
  99100644 0aa34cae68d0878578ad119c86ca2b5ed5b28376 0       path3/file3
 100120000 8599103969b43aff7e430efea79ca4636466794f 0       path3/file3sym
 101100644 00fb5908cb97c2564a9783c0c64087333b3b464f 0       path3/subp3/file3
 102120000 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c 0       path3/subp3/file3sym
 103EOF
 104test_expect_success \
 105    'validate git-ls-files output for a known tree.' \
 106    'diff current expected'
 107
 108test_expect_success \
 109    'writing tree out with git-write-tree.' \
 110    'tree=$(git-write-tree)'
 111test_expect_success \
 112    'validate object ID for a known tree.' \
 113    'test "$tree" = 087704a96baf1c2d1c869a8b084481e121c88b5b'
 114
 115test_expect_success \
 116    'showing tree with git-ls-tree' \
 117    'git-ls-tree $tree >current'
 118cat >expected <<\EOF
 119100644 blob f87290f8eb2cbbea7857214459a0739927eab154    path0
 120120000 blob 15a98433ae33114b085f3eb3bb03b832b3180a01    path0sym
 121040000 tree 58a09c23e2ca152193f2786e06986b7b6712bdbe    path2
 122040000 tree 21ae8269cacbe57ae09138dcc3a2887f904d02b3    path3
 123EOF
 124test_expect_success \
 125    'git-ls-tree output for a known tree.' \
 126    'diff current expected'
 127
 128test_expect_success \
 129    'showing tree with git-ls-tree -r' \
 130    'git-ls-tree -r $tree >current'
 131cat >expected <<\EOF
 132100644 blob f87290f8eb2cbbea7857214459a0739927eab154    path0
 133120000 blob 15a98433ae33114b085f3eb3bb03b832b3180a01    path0sym
 134040000 tree 58a09c23e2ca152193f2786e06986b7b6712bdbe    path2
 135100644 blob 3feff949ed00a62d9f7af97c15cd8a30595e7ac7    path2/file2
 136120000 blob d8ce161addc5173867a3c3c730924388daedbc38    path2/file2sym
 137040000 tree 21ae8269cacbe57ae09138dcc3a2887f904d02b3    path3
 138100644 blob 0aa34cae68d0878578ad119c86ca2b5ed5b28376    path3/file3
 139120000 blob 8599103969b43aff7e430efea79ca4636466794f    path3/file3sym
 140040000 tree 3c5e5399f3a333eddecce7a9b9465b63f65f51e2    path3/subp3
 141100644 blob 00fb5908cb97c2564a9783c0c64087333b3b464f    path3/subp3/file3
 142120000 blob 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c    path3/subp3/file3sym
 143EOF
 144test_expect_success \
 145    'git-ls-tree -r output for a known tree.' \
 146    'diff current expected'
 147
 148################################################################
 149rm .git/index
 150test_expect_success \
 151    'git-read-tree followed by write-tree should be idempotent.' \
 152    'git-read-tree $tree &&
 153     test -f .git/index &&
 154     newtree=$(git-write-tree) &&
 155     test "$newtree" = "$tree"'
 156
 157cat >expected <<\EOF
 158:100644 100644 f87290f8eb2cbbea7857214459a0739927eab154 0000000000000000000000000000000000000000 M      path0
 159:120000 120000 15a98433ae33114b085f3eb3bb03b832b3180a01 0000000000000000000000000000000000000000 M      path0sym
 160:100644 100644 3feff949ed00a62d9f7af97c15cd8a30595e7ac7 0000000000000000000000000000000000000000 M      path2/file2
 161:120000 120000 d8ce161addc5173867a3c3c730924388daedbc38 0000000000000000000000000000000000000000 M      path2/file2sym
 162:100644 100644 0aa34cae68d0878578ad119c86ca2b5ed5b28376 0000000000000000000000000000000000000000 M      path3/file3
 163:120000 120000 8599103969b43aff7e430efea79ca4636466794f 0000000000000000000000000000000000000000 M      path3/file3sym
 164:100644 100644 00fb5908cb97c2564a9783c0c64087333b3b464f 0000000000000000000000000000000000000000 M      path3/subp3/file3
 165:120000 120000 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c 0000000000000000000000000000000000000000 M      path3/subp3/file3sym
 166EOF
 167test_expect_success \
 168    'validate git-diff-files output for a know cache/work tree state.' \
 169    'git-diff-files >current && diff >/dev/null -b current expected'
 170
 171test_expect_success \
 172    'git-update-cache --refresh should succeed.' \
 173    'git-update-cache --refresh'
 174
 175test_expect_success \
 176    'no diff after checkout and git-update-cache --refresh.' \
 177    'git-diff-files >current && cmp -s current /dev/null'
 178
 179test_done