mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2024-11-10 23:00:57 +00:00
7bfaa24d25
Details in README.md and s3fs-integration-test-common.sh Factor out s3fs-fuse and s3proxy start/stop. The plan is to make it easier to add test suites besides small-integration-test.sh that can test with various s3fs options. Each test run starts in a uniquely named at the top of the bucket. This allows multiple runs against persistent storage without worrying about cleaning up in error conditions that leave artifiacts behind. Tests continues if a test case fails. Results are summarized at the end of the test run Environment variable to control debug level of s3fs-fuse Environment variable to enable public bucket (makes it easier to poke around with tools like curl) Environment variable to start s3fs-fuse under valgrind Environment variable that casues script sets up s3fs-fuse and then wait indefinitely, making it easy to experiment manually with the mount point. Additional test case
31 lines
670 B
Bash
Executable File
31 lines
670 B
Bash
Executable File
#!/bin/bash
|
|
|
|
#
|
|
# Test s3fs-fuse file system operations with
|
|
#
|
|
|
|
set -o errexit
|
|
|
|
# Require root
|
|
REQUIRE_ROOT=require-root.sh
|
|
#source $REQUIRE_ROOT
|
|
|
|
source integration-test-common.sh
|
|
|
|
start_s3proxy
|
|
|
|
#
|
|
# enable_content_md5
|
|
# Causes s3fs to validate file contents. This isn't included in the common
|
|
# options used by start_s3fs because tests may be performance tests
|
|
# singlepart_copy_limit
|
|
# Appeared in upstream s3fs-fuse tests, possibly a limitation of S3Proxy
|
|
# TODO: github archaeology to see why it was added.
|
|
#
|
|
start_s3fs -o enable_content_md5 \
|
|
-o singlepart_copy_limit=$((10 * 1024))
|
|
|
|
./integration-test-main.sh
|
|
|
|
echo "$0: tests complete."
|