Test Batch Runner: Does it work well?
I was just looking at the Test Batch Runner documentation and it looks bad.
"Give your batch file a meaningful name and assign it to a place in your directory."
"New Batch" button is being called "New batch file button"
Even the About Test Batch Runner dialog is not properly displaying things ("T" in Test, "V" in version, and the copyright symbol are not properly displayed.
and many more.
One of these days, I will give this tool a try.
Does Test Batch Runner work well?
Supports tests in different frameworks? (hybrid, etc.)
Nothing to change in the Initialization Settings?
Please share your Good and Bad experiences with it, tips/clues from what you've learned from using it.
Last edited by Gilbert; 01-12-2015 at 12:08 PM.
Reason: added more details
I tried it a few years ago. It worked. It was not flexible or controllable. I wound up writing a .vbs script that connects to an Excel WB. Then it would run one script at a time. I could make it do all types of things such as collect some fail data. Have one script only run if anohter one passed.