Not sure about the Linux question (although I am interested in the answer because I want to do the same thing).
I am currently using SilkTest to automate a CLI. It's a bit kludgy and I'm not sure it would work or be practical for your application, but I'm opening a telnet session, using TypeKeys methods to enter commands defined through LIST OF STRING constants, logging the telnet output to a file, and then opening the log file with Notepad and using Notepad's search dialog to find the appropriate output values.
[This message has been edited by dano (edited 09-28-2001).]
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by dano: [..] then opening the log file with Notepad and using Notepad's search dialog to find the appropriate output values. <HR></BLOCKQUOTE>
You might like create a list of string with SYS_GetFileContents() and use the MatchStr() function for the "patterns" you are looking for. This surely should be more relyable than the Notepad solution.
Can you please be more elaborative on how you are redirecting the telnet output to file.
Also I have some isuues in testing a cli as follows: My cli will be used by telneting or by doing ssh to the Linux box on which Server demon is running.
What all considerations should be there from compatibility point of view.
I mean user may telnet from Windows machine or machine with any OS. So shall i need to try for differnet versions of telnet and ssh or it should not matter.
Also I need some guidance on negative testing of commands. What should be the tentitive checklist.
Like boundary values for command inputs. Invalid values. valid values.etc.