Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Complete the rename to backup-bouncer.

git-svn-id: svn+ssh://svn.n8gray.org/svnroot/n8gray/public/backup-bouncer@98 c73bc784-a200-0410-bfa9-bab0993648b8
  • Loading branch information...
commit 5badf7af71f0e480a65896fa47ef1d688fd5029c 1 parent ce96b92
n8gray authored
View
2  LICENSE
@@ -1,4 +1,4 @@
-License for backup-test
+License for backup-bouncer
Copyright 2007 by Nathaniel Gray <n8gray /at/ n8gray \dot\ org>
View
12 README
@@ -1,5 +1,5 @@
-backup-test
-===========
+backup-bouncer
+==============
A unit-testing framework for OS X backup tools.
Written by Nathaniel Gray.
@@ -26,7 +26,7 @@ required:
* SetFile
* GetFileInfo
-These are included with the XCode developer tools, and backup-test expects them
+These are included with the XCode developer tools, and bbouncer expects them
to be in /Developer/Tools. If they're not there for some reason, add their
location to your PATH and all will be well.
@@ -37,7 +37,7 @@ Installation & Usage
1. run "make"
2. there's no step 2.
-You can now run "backup-test" with no arguments for usage info. Or, you can run
+You can now run "bbouncer" with no arguments for usage info. Or, you can run
"./autopilot" to automatically generate some disk images, run all tests, and see
the results.
@@ -56,7 +56,7 @@ Adding tests is easy! Just copy an existing test and fill in the functions.
Take a look at tests.d/00-basic-permissions.test for comments on the arguments
and expected behavior of each function.
-After you add a test you need to re-run 'backup-test create' on your source
+After you add a test you need to re-run 'bbouncer create' on your source
volume.
Adding Copiers
@@ -67,7 +67,7 @@ in the functions. See copiers.d/10-rsync-apple.cp for comments on the arguments
and expected behavior of each function.
You should understand that you don't have to add a copier to test your favorite
-copy mechanism. You can do the copy by hand and then use 'backup-test verify'
+copy mechanism. You can do the copy by hand and then use 'bbouncer verify'
to do the verification. Copiers are just there to ease automated testing.
History
View
8 autopilot
@@ -7,7 +7,7 @@ echo
set -ex
make
-./backup-test create-vol Src
-./backup-test create-vol Dst
-./backup-test create /Volumes/Src
-./backup-test copy -d /Volumes/Src /Volumes/Dst
+./bbouncer create-vol Src
+./bbouncer create-vol Dst
+./bbouncer create /Volumes/Src
+./bbouncer copy -d /Volumes/Src /Volumes/Dst
View
10 backup-test → bbouncer
@@ -9,7 +9,7 @@ export PATH="`pwd`/util:/Developer/Tools:$PATH:."
export printWidth=20
usage () {
- name=backup-test
+ name=bbouncer
echo "Usage:
General form:
$name <verb> [-d] [-t test]* [-T set] [-c copier]* args
@@ -106,14 +106,14 @@ create-vol () {
-volname $1 -type SPARSE ./$1
hdiutil attach -owners on ./$1.sparseimage
sudo fsaclctl -p /Volumes/$1 -e
- touch /Volumes/$1/backup-test-vol
+ touch /Volumes/$1/bbouncer-vol
}
check-vol () {
- if [ -e $1/backup-test-vol ]; then
+ if [ -e $1/bbouncer-vol ]; then
return 0
else
- echo "$1 is not a backup-test volume! Aborting." 1>&2
+ echo "$1 is not a bbouncer volume! Aborting." 1>&2
exit 1
fi
}
@@ -219,7 +219,7 @@ copy () {
code=$?
echo $code > $dst/$c/exit-code
# Make sure the volume can be cleaned
- touch $dst/$c/backup-test-vol
+ touch $dst/$c/bbouncer-vol
[ "$code" = "0" ] && echo ok \
|| echo FAIL
done
View
2  copiers.d/70-xar.cp
@@ -19,7 +19,7 @@ version () {
backup () {
cd $1
# xar doesn't work with pipes yet, so we use a tmpfile
- tmpfile=`mktemp -t backup-test-xar` || exit 1
+ tmpfile=`mktemp -t bbouncer-xar` || exit 1
sudo $xar -c -f $tmpfile . \
&& cd $2 \
&& sudo $xar -x -f $tmpfile
View
2  scripts/test-asr
@@ -19,4 +19,4 @@ uname -a > $2/meta
echo >> $2/meta
$asr --version 2>> $2/meta
-./backup-test verify -d $1 $2 | tee $2/verify-output
+./bbouncer verify -d $1 $2 | tee $2/verify-output
Please sign in to comment.
Something went wrong with that request. Please try again.