luasocket/test
Diego Nehab 0b2542d1a6 Worked on the manual.
Implemented stuffing (needs test)
Added cddb and qp examples.
2004-02-04 14:29:11 +00:00
..
auth http.lua updated. still needs proxy support. 2004-01-16 07:06:31 +00:00
cgi The test directory! 2003-03-21 23:49:18 +00:00
ftptest.lua Starting to use RCS in princeton again. Not behind a firewall anymore. 2003-08-31 00:58:07 +00:00
httptest.lua Working on the manual... 2004-01-24 02:47:24 +00:00
index.html The test directory! 2003-03-21 23:49:18 +00:00
mimetest.lua Worked on the manual. 2004-02-04 14:29:11 +00:00
README And this. 2003-06-30 18:57:07 +00:00
smtptest.lua Adjusted a few inconsistencies with the manual. 2003-08-16 00:06:04 +00:00
testclnt.lua Worked on the manual. 2004-02-04 14:29:11 +00:00
testsrvr.lua Adjusted wsocket to match usocket. Adjusted windows projects. 2004-01-21 20:16:48 +00:00
tftptest.lua Porting to LUA 5.0 final 2003-05-25 01:54:13 +00:00
upload.html The test directory! 2003-03-21 23:49:18 +00:00
urltest.lua Worked on the manual. 2004-02-04 14:29:11 +00:00

This provides the  automated test scripts used to make  sure the library
is working properly.

The files provided are:

    testsrvr.lua            -- test server
    testclnt.lua            -- test client
    testcmd.lua             -- test command definitions

To run  the automatic  tests on  your system, make  sure to  compile the
library  with  _DEBUG  defined  (check   makefile)  and  then  open  two
terminals. Run  'luasocket testsrvr.lua' on  one of them  and 'luasocket
testclnt.lua' on  the other. The  programs should start talking  to each
other and report any failure. The tests can also be used as a benchmark.

    urltest.lua             -- url.lua test module
    codetest.lua            -- code.lua test module
    concattest.lua          -- concat.lua test module

To run these tests, just run luasocket on them and see the results.

Good luck,
Diego.