On Wed, May 13, 2009 at 1:01 PM, James Hawkins truiken@gmail.com wrote:
On Wed, May 13, 2009 at 10:27 AM, Austin English austinenglish@gmail.com wrote:
Howdy all,
I've been working on the test suite. I've got a few basic tests set up with notepad, and I'm currently working on setting up the framework, using AutoHotKey to both run all the tests and parse the logs for failures/passing todo's.
For those interested, here's the first 'real' script I've written. It sets up a test directory (C:\appinstall), downloads sha1sum.exe (if it doesn't exist), verifies its own sha1sum, downloads winscp.exe (portable version), sets up winscp.ini with its settings (I was going to use keyboard/mouse control, but ftp.winehq.org times out to quickly, and adjusting that setting with mouse/keyboard would be a lot more trouble), runs winscp, downloads welcome.msg, closes winscp, sha1sum's welcome.msg, and finally, deletes welcome.msg and winscp.ini.
This should probably be done in a temporary directory instead of hard-coded to C:\appinstall.
Of course. I'm working on changing any temporary stuff to %TEMP%\appinstall.
The reason for C:\appinstall (more accurately, %SYSTEMDIR%, so it will work on Windows installs without a C:\ drive) is to cache downloads. That way sha1sum.exe, wget.exe, etc. don't have to be downloaded repeatedly (they are still sha1sum'ed before use). I'm thinking a bit ahead, that way we can test, e.g., Photoshop CS 3, which has a download available, but not one that is scriptable. That way, if someone running the script already has CS 3 in place, the test is run. Else, it will get skipped, saying 'photoshop isn't available, download manually and place in C:\appinstall if you want to test it'.