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 258 subdirectories; 256 fan-out, pack, and info.
  32# 259 is counting "objects" itself
  33find .git/objects -type d -print >full-of-directories
  34test_expect_success \
  35    '.git/objects should have 258 subdirectories.' \
  36    'test $(wc -l < full-of-directories) = 259'
  37
  38################################################################
  39# Basics of the basics
  40
  41# updating a new file without --add should fail.
  42test_expect_failure \
  43    'git-update-cache without --add should fail adding.' \
  44    'git-update-cache should-be-empty'
  45
  46# and with --add it should succeed, even if it is empty (it used to fail).
  47test_expect_success \
  48    'git-update-cache with --add should succeed.' \
  49    'git-update-cache --add should-be-empty'
  50
  51test_expect_success \
  52    'writing tree out with git-write-tree' \
  53    'tree=$(git-write-tree)'
  54
  55# we know the shape and contents of the tree and know the object ID for it.
  56test_expect_success \
  57    'validate object ID of a known tree.' \
  58    'test "$tree" = 7bb943559a305bdd6bdee2cef6e5df2413c3d30a'
  59
  60# Removing paths.
  61rm -f should-be-empty full-of-directories
  62test_expect_failure \
  63    'git-update-cache without --remove should fail removing.' \
  64    'git-update-cache should-be-empty'
  65
  66test_expect_success \
  67    'git-update-cache with --remove should be able to remove.' \
  68    'git-update-cache --remove should-be-empty'
  69
  70# Empty tree can be written with recent write-tree.
  71test_expect_success \
  72    'git-write-tree should be able to write an empty tree.' \
  73    'tree=$(git-write-tree)'
  74
  75test_expect_success \
  76    'validate object ID of a known tree.' \
  77    'test "$tree" = 4b825dc642cb6eb9a060e54bf8d69288fbee4904'
  78
  79# Various types of objects
  80mkdir path2 path3 path3/subp3
  81for p in path0 path2/file2 path3/file3 path3/subp3/file3
  82do
  83    echo "hello $p" >$p
  84    ln -s "hello $p" ${p}sym
  85done
  86test_expect_success \
  87    'adding various types of objects with git-update-cache --add.' \
  88    'find path* ! -type d -print0 | xargs -0 git-update-cache --add'
  89
  90# Show them and see that matches what we expect.
  91test_expect_success \
  92    'showing stage with git-ls-files --stage' \
  93    'git-ls-files --stage >current'
  94
  95cat >expected <<\EOF
  96100644 f87290f8eb2cbbea7857214459a0739927eab154 0       path0
  97120000 15a98433ae33114b085f3eb3bb03b832b3180a01 0       path0sym
  98100644 3feff949ed00a62d9f7af97c15cd8a30595e7ac7 0       path2/file2
  99120000 d8ce161addc5173867a3c3c730924388daedbc38 0       path2/file2sym
 100100644 0aa34cae68d0878578ad119c86ca2b5ed5b28376 0       path3/file3
 101120000 8599103969b43aff7e430efea79ca4636466794f 0       path3/file3sym
 102100644 00fb5908cb97c2564a9783c0c64087333b3b464f 0       path3/subp3/file3
 103120000 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c 0       path3/subp3/file3sym
 104EOF
 105test_expect_success \
 106    'validate git-ls-files output for a known tree.' \
 107    'diff current expected'
 108
 109test_expect_success \
 110    'writing tree out with git-write-tree.' \
 111    'tree=$(git-write-tree)'
 112test_expect_success \
 113    'validate object ID for a known tree.' \
 114    'test "$tree" = 087704a96baf1c2d1c869a8b084481e121c88b5b'
 115
 116test_expect_success \
 117    'showing tree with git-ls-tree' \
 118    'git-ls-tree $tree >current'
 119cat >expected <<\EOF
 120100644 blob f87290f8eb2cbbea7857214459a0739927eab154    path0
 121120000 blob 15a98433ae33114b085f3eb3bb03b832b3180a01    path0sym
 122040000 tree 58a09c23e2ca152193f2786e06986b7b6712bdbe    path2
 123040000 tree 21ae8269cacbe57ae09138dcc3a2887f904d02b3    path3
 124EOF
 125test_expect_success \
 126    'git-ls-tree output for a known tree.' \
 127    'diff current expected'
 128
 129test_expect_success \
 130    'showing tree with git-ls-tree -r' \
 131    'git-ls-tree -r $tree >current'
 132cat >expected <<\EOF
 133100644 blob f87290f8eb2cbbea7857214459a0739927eab154    path0
 134120000 blob 15a98433ae33114b085f3eb3bb03b832b3180a01    path0sym
 135040000 tree 58a09c23e2ca152193f2786e06986b7b6712bdbe    path2
 136100644 blob 3feff949ed00a62d9f7af97c15cd8a30595e7ac7    path2/file2
 137120000 blob d8ce161addc5173867a3c3c730924388daedbc38    path2/file2sym
 138040000 tree 21ae8269cacbe57ae09138dcc3a2887f904d02b3    path3
 139100644 blob 0aa34cae68d0878578ad119c86ca2b5ed5b28376    path3/file3
 140120000 blob 8599103969b43aff7e430efea79ca4636466794f    path3/file3sym
 141040000 tree 3c5e5399f3a333eddecce7a9b9465b63f65f51e2    path3/subp3
 142100644 blob 00fb5908cb97c2564a9783c0c64087333b3b464f    path3/subp3/file3
 143120000 blob 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c    path3/subp3/file3sym
 144EOF
 145test_expect_success \
 146    'git-ls-tree -r output for a known tree.' \
 147    'diff current expected'
 148
 149################################################################
 150rm .git/index
 151test_expect_success \
 152    'git-read-tree followed by write-tree should be idempotent.' \
 153    'git-read-tree $tree &&
 154     test -f .git/index &&
 155     newtree=$(git-write-tree) &&
 156     test "$newtree" = "$tree"'
 157
 158cat >expected <<\EOF
 159:100644 100644 f87290f8eb2cbbea7857214459a0739927eab154 0000000000000000000000000000000000000000 M      path0
 160:120000 120000 15a98433ae33114b085f3eb3bb03b832b3180a01 0000000000000000000000000000000000000000 M      path0sym
 161:100644 100644 3feff949ed00a62d9f7af97c15cd8a30595e7ac7 0000000000000000000000000000000000000000 M      path2/file2
 162:120000 120000 d8ce161addc5173867a3c3c730924388daedbc38 0000000000000000000000000000000000000000 M      path2/file2sym
 163:100644 100644 0aa34cae68d0878578ad119c86ca2b5ed5b28376 0000000000000000000000000000000000000000 M      path3/file3
 164:120000 120000 8599103969b43aff7e430efea79ca4636466794f 0000000000000000000000000000000000000000 M      path3/file3sym
 165:100644 100644 00fb5908cb97c2564a9783c0c64087333b3b464f 0000000000000000000000000000000000000000 M      path3/subp3/file3
 166:120000 120000 6649a1ebe9e9f1c553b66f5a6e74136a07ccc57c 0000000000000000000000000000000000000000 M      path3/subp3/file3sym
 167EOF
 168test_expect_success \
 169    'validate git-diff-files output for a know cache/work tree state.' \
 170    'git-diff-files >current && diff >/dev/null -b current expected'
 171
 172test_expect_success \
 173    'git-update-cache --refresh should succeed.' \
 174    'git-update-cache --refresh'
 175
 176test_expect_success \
 177    'no diff after checkout and git-update-cache --refresh.' \
 178    'git-diff-files >current && cmp -s current /dev/null'
 179
 180test_done