github/rclone
1
Fork 0
mirror of https://github.com/rclone/rclone synced 2024-12-23 14:23:44 +01:00
Code Releases Activity
7c98ecd3ab
rclone/fstest/testserver/init.d
History
Nick Craig-Wood bd9fd629bc test: add TestS3MinioEdge to test leading edge minio too #3934
2020-02-13 11:01:06 +00:00
..
docker.bash build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
README.md build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
run.bash build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestFTPProftpd build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestFTPPureftpd build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestFTPRclone build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestFTPVsftpd build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestS3Minio testserver: add provider to TestS3Minio #3934 2020-02-13 11:01:06 +00:00
TestS3MinioEdge test: add TestS3MinioEdge to test leading edge minio too #3934 2020-02-13 11:01:06 +00:00
TestSFTPOpenssh build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestSFTPRclone build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestSwiftAIO build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestWebdavNextcloud build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestWebdavOwncloud build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00
TestWebdavRclone build: implement a framework for starting test servers during tests 2020-01-18 16:47:37 +00:00

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