In my company, I had to do also an automated test suite.
I began with batch files, because there were already some very basic scripts done by another developer and I as extending them.
But, the suite needed some more advanced things, like time profiling. Batch files were too bad to do time calculations, even the simplest.
So, I decided to migrate to a scripting language, and I was between Tcl (I already did things with it, even controlling Networking printers through SNMP and PCL) and Python (Never touched it).
Even I like more the Tcl syntax, I decided for Python, because:
- Python has a more active community and is not dying, unlike Tcl
- I could learn Python
- I could get help from some colleagues at my job
- If the thing needs to be maintained, it will is more likely to get people that knows Python than Tcl
- It has some modern developments that Tcl does not have
But, I also had some problems. First Python is now in a phase of deep restructuring, and I was doing it in Python 3 and had lots of problems, mainly because of some extras for Python that are not compatible. After, I discovered a chat Channel whose topic says "It's to early to use Python 3".
So I downgraded it and got the job done. So, if you go for Python, I recommend seriously 2.6
And you can also have some Windows things, may be it is why you are reticent of moving out from batches. I used winreg module to access the Windows registry.