We need a test harness developed that will test every
possible protocol against all the others to make sure the
pluggins are functionally completed.
The base for this already exist in the ftester directory.
An ant task "ftester" compiles and generates code from
the testprotocol.ramp file. Right now it generates for a
c client, c server, java client, java server. After that
running the ftester will run each client against each
server.
This system needs to be automated and setup to scale
for more pluggins as they are created. The end result of
the test should come back as a matrix showing the
clients on the top, servers on the side and then a listing
of what passed and failed on the grid.
Log in to post a comment.
