libgocryptfs/test.bash

#!/bin/bash

set -eu

cd "$(dirname "$0")"

source build.bash

go test ./... $*

# Clean up after ourself, but don't descend into maybe still mounted
# example filesystems
# The tests cannot to this themselves as they are run in parallel
rm -Rf --one-file-system /tmp/gocryptfs-test-parent

go tool vet -shadow=true .
Add test.bash ...also adapt the cryptfs tests for 256 bit long keys 2015-10-07 22:08:30 +02:00			`#!/bin/bash`

tests: reduce noise but make test.bash accept "-v" 2015-11-03 21:11:07 +01:00			`set -eu`
Add test.bash ...also adapt the cryptfs tests for 256 bit long keys 2015-10-07 22:08:30 +02:00
Make test.bash work when called from outside the gocryptfs directory Also, get rid of useless intermediate build step 2016-01-09 14:20:04 +01:00			`cd "$(dirname "$0")"`

Update test.bash to call build.bash This makes sure the version number is baked into the binary that is built 2015-11-01 15:22:53 +01:00			`source build.bash`
Fix tests - were broken by the refactoring 2016-02-06 20:22:45 +01:00
test.bash: Accept flags 2016-02-06 20:25:18 +01:00			`go test ./... $*`
Fix "go tool vet -shadow=true" warnings Among those one real bug. 2016-04-10 21:29:42 +02:00
test: split up integration_tests ...into "matrix" and "normal". Also: * Make running multiple packages in parallel safe, see http://stackoverflow.com/questions/23715302/go-how-to-run-tests-for-multiple-packages * Don't depent on test_helper.TmpDir and friends to have a terminating slash 2016-06-30 00:57:14 +02:00			`# Clean up after ourself, but don't descend into maybe still mounted`
			`# example filesystems`
			`# The tests cannot to this themselves as they are run in parallel`
			`rm -Rf --one-file-system /tmp/gocryptfs-test-parent`

Fix "go tool vet -shadow=true" warnings Among those one real bug. 2016-04-10 21:29:42 +02:00			`go tool vet -shadow=true .`