NameLast commit messageLast commit date
..
seafileseafile: New backend for seafile server6 years ago
docker.bashbuild: implement a framework for starting test servers during tests7 years ago
README.mdbuild: implement a framework for starting test servers during tests7 years ago
run.bashbuild: implement a framework for starting test servers during tests7 years ago
TestFTPProftpdbuild: implement a framework for starting test servers during tests7 years ago
TestFTPPureftpdbuild: implement a framework for starting test servers during tests7 years ago
TestFTPRclonebuild: implement a framework for starting test servers during tests7 years ago
TestFTPVsftpdbuild: implement a framework for starting test servers during tests7 years ago
TestS3Miniotestserver: add provider to TestS3Minio #39346 years ago
TestS3MinioEdgetest: add TestS3MinioEdge to test leading edge minio too #39346 years ago
TestSeafileseafile: New backend for seafile server6 years ago
TestSeafileEncryptedseafile: New backend for seafile server6 years ago
TestSeafileV6seafile: New backend for seafile server6 years ago
TestSFTPOpensshbuild: implement a framework for starting test servers during tests7 years ago
TestSFTPRclonebuild: implement a framework for starting test servers during tests7 years ago
TestSwiftAIObuild: implement a framework for starting test servers during tests7 years ago
TestWebdavNextcloudbuild: implement a framework for starting test servers during tests7 years ago
TestWebdavOwncloudbuild: implement a framework for starting test servers during tests7 years ago
TestWebdavRclonebuild: implement a framework for starting test servers during tests7 years ago
README.md

This directory contains scripts to start and stop servers for testing.

The commands are named after the remotes in use. They should be executable files with the following parameters:

start  - starts the server
stop   - stops the server
status - returns non-zero exit code if the server is not running

These will be called automatically by test_all if that remote is required.

When start is run it should output config parameters for that remote. If a _connect parameter is output then that will be used for a connection test. For example if _connect=127.0.0.1:80 then a TCP connection will be made to 127.0.0.1:80 and only when that succeeds will the test continue.

run.bash contains boilerplate to be included in a bash script for interpreting the command line parameters.

docker.bash contains library functions to help with docker implementations.

TODO