Jakob Unterwurzacher 3f5c48e058 tests: don't call t.Fatal in checkExampleFS ...

Calling t.Fatal means that the parent test has no chance
to clean up.

2016-11-26 15:20:54 +01:00

..

content

tests: add v1.1-aessiv example filesystem

2016-10-08 21:45:01 +02:00

v0.4

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v0.5

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v0.6

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v0.6-plaintextnames

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v0.7

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v0.7-plaintextnames

tests: add v0.7-plaintextnames example filesystem

2016-06-23 20:53:14 +02:00

v0.9

tests: split example_filesystems into its own package

2016-06-07 00:08:56 +02:00

v1.1-aessiv

tests: add v1.1-aessiv example filesystem

2016-10-08 21:45:01 +02:00

v1.1-reverse

tests: add v1.1-reverse example filesystem

2016-10-08 21:45:11 +02:00

v1.1-reverse-plaintextnames

tests: add v1.1-reverse-plaintextnames example filesystem

2016-10-08 21:49:21 +02:00

example_filesystems_test.go

reverse: gocryptfs.conf was missing from the directory listings

2016-10-08 22:25:08 +02:00

example_test_helpers.go

tests: don't call t.Fatal in checkExampleFS

2016-11-26 15:20:54 +01:00