test/sharness: Add sharness v1.0.0 as a submodule

It's GPLv2+ [1], so using a submodule keeps the separation from our
Apache 2.0 source clear.  And it's an isolated enough dependency that
I prefer to keep the Git histories separate.

Generated with:

  $ mkdir test
  $ git submodule add git://github.com/mlafeldt/sharness.git test/sharness
  $ (cd test/sharness && git checkout v1.0.0)
  $ git add test/sharness
  $ cd test
  $ ln -s sharness/aggregate-results.sh
  $ ln -s sharness/sharness.sh
  $ ln -s sharness/test/Makefile
  $ emacs README.md
  $ git add README.md Makefile sharness.sh aggregate-results.sh

[1]: https://github.com/mlafeldt/sharness/tree/v1.0.0#license

Signed-off-by: W. Trevor King <wking@tremily.us>

Author: wking

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "test/sharness"]
+	path = test/sharness
+	url = git://github.com/mlafeldt/sharness.git

test/Makefile

@@ -0,0 +1 @@
+sharness/test/Makefile

test/README.md

@@ -0,0 +1,22 @@
+# Ocitools integration tests
+
+Ocitools uses the [Sharness][] test harness, installed as a [Git
+submodule]submodule].  To setup the test installation after a clone,
+run:
+
+    $ git submodule update --init
+
+which will checkout the appropriate Sharness commit in the `sharness`
+directory (after which the `Makefile`, `sharness.sh`, etc. symlinks
+will resolve successfully).
+
+Run the tests with:
+
+    $ make
+
+And read the `Makefile` source to find other useful targets
+(e.g. [`prove`][prove]).
+
+[prove]: http://perldoc.perl.org/prove.html
+[Sharness]: http://mlafeldt.github.io/sharness/
+[submodule]: http://git-scm.com/docs/git-submodule

test/aggregate-results.sh

@@ -0,0 +1 @@
+sharness/aggregate-results.sh

test/sharness

@@ -0,0 +1 @@
+sharness/sharness.sh