02| IF TESTS DO NOT PASS
03| OTHER
—01| HOW TO USE THIS DOCUMENT
The FTP tests will not work unless you do set up. To run the FTP tests, you need to do the following:
- Set up a remote machine with an FTP server on it. This is where the code will download from and upload to.
- Copy the contents of the
ftp-remote
directory to the machine with the FTP server. You can use an FTP client to do this. You may or may not have to set permissions on the directories, depending on how your machine is set up. That is another topic that you would have to research for your FTP software and/or OS, but it may be as simple as doing a chmod on the directory. - Open
ftp-test-config.tcl
and set the values for your setup (e.g. IP address, etc.). The comments in that file and doc/about-ftp-use.html should help you. - To get some tests to pass, the local copy must be newer than the remote. So you might want to go through
ftp-local/original/different-times
and touch alllocal-newer*.txt
files. - The tests use a diff command to check if the results match what is expected. You may need to install diff software.
That should be it. You should now be able to run all.tcl or individual ftp*.test files and (hopefully) have them pass.
—02| GETTING SET UP TO RUN TESTS
If you get failures, be aware you can do ...
set GenNS::DebugOn 1
... which is an internal feature, likely to change, but available as-is for helping with FTP issues. If you run the tests again, you will get output that may help you with figuring out the root cause of the problem.
—03| OTHER
Note that all the tests are set up to run with binary transfer type. ASCII has not been tested because have not decided how to handle the fact that results may be different depending on what kind of machines are used in the tests.
For more information about FTP use, see doc/about-ftp-use.html.