• Home
  • History
  • Annotate
  • only in /external/mockftpserver/tags/2.2/
NameDateSize

..23-Aug-20164 KiB

.classpath23-Aug-20161.9 KiB

.project23-Aug-2016579

.settings/23-Aug-20164 KiB

CHANGELOG.txt23-Aug-20169.2 KiB

LICENSE.txt23-Aug-201611.3 KiB

MockFtpServer.iml23-Aug-2016266

MockFtpServer.ipr23-Aug-201616.8 KiB

pom.xml23-Aug-20168.5 KiB

README.txt23-Aug-20161.5 KiB

src/23-Aug-20164 KiB

README.txt

1MockFtpServer version ${project.version}
2-------------------------------------------------------------------------------
3${project.url}
4
5The MockFtpServer project provides mock/dummy FTP server implementations for testing FTP client
6code. Two FTP Server implementations are provided, each at a different level of abstraction.
7
8FakeFtpServer provides a higher-level abstraction. You define a virtual file system, including
9directories and files, as well as a set of valid user accounts and credentials. The FakeFtpServer
10then responds with appropriate replies and reply codes based on that configuration.
11
12StubFtpServer, on the other hand, is a lower-level "stub" implementation. You configure the
13individual FTP server commands to return custom data or reply codes, allowing simulation of
14either success or failure scenarios. You can also verify expected command invocations.
15
16MockFtpServer is written in Java, and is ideally suited to testing Java code. But because
17communication with the FTP server is across sockets and TCP/IP, it can be used to test FTP client 
18code written in any language.
19
20See the online documentation for more information.
21
22See the FTP Protocol Spec (http://www.ietf.org/rfc/rfc0959.txt) for information about 
23FTP, commands, reply codes, etc..
24
25DEPENDENCIES
26
27MockFtpServer requires 
28 - Java (JDK) version 1.4 or later
29 - The Log4J jar, version 1.2.13 or later, accessible on the CLASSPATH
30   (http://logging.apache.org/log4j/index.html).
31