Jules -
There are lots of solutions for automating software testing out there.
I built in a past life a system (Hammer Technologies' Hammer) for
beating on voicemail systems over the telephone network so that these
systems could be load tested without 150 humans calling in at one time
(and believe me we did live tests in the early days on voicemail systems
just like that!!!). Even patented a speech recognition approach to make
sure the voicemail systems were responding properly.
Similarly there are software systems that will duplicate any specified
series of actions that a human (or computer) might take in order to
simulate a user and (in most cases) record the results. This of course
only measures the "outsiders'" view of what is going on, and doesn't
look at the internals of the stack or anything else. But it does make
for a useful tool to evaluate remotely whether something is still
running. Many of the large financial services companies with complex
financial software running for their customers use similar systems today
to monitor their uptime and catch problems before they affect too many
users.
I've been out of it way too long to know who is current with the best
solutions, but companies like
Empirix.com (where my company Hammer
Technologies eventually ended up) do similar things today. There have
got to be some shareware systems somewhere that do this. Anyone running
a UNIX box out there ought to be able to write a shell script to test
Mike's setup and record the responses. It will be easier when a "pcjr>"
response prompt is implemented so that there is a real response to check
on the way back...otherwise the user is forced to just wait and then
type a command that should return something like "help" or "nicks"
John Kuenzig
Jules Richardson wrote:
Philip Pemberton wrote:
I did come up with one "nice to have"
-- is there any chance of
adding a prompt character/string to it, say "pcjr> " or similar? Just
that I thought it had fallen over after the MOTD until I typed
"help<CR>" and it actually *worked*...
Yeah, that 'bit' me, too.
Re. testing, is there any way to write something that runs on remote
systems and just hammers the network stack / telnet interface on the
PCjr, or does nothing like that exist already? It seems like so many
TCP/IP stacks have been written for various machines over the years
that it surprises me nobody's come up with a solution for automating
some of the testing.
cheers
Jules