Thanks for the information, TNeuschwanger . I'll look that over. One of my issues with the existing logging and reporting is that it only reports the failure at the test case level. We utilize Grid Data Sources, where each row in the grid is a separate test case. I need to be able to easily see which of those test cases (rows) are failing, rather than just the overall test case.
I'm open to any other ideas you may have.
Hello bbrown1
Well, the results you get from running from the command line are different that a general report. It actually generates a text file for every test step executed, not just the test case as a whole. You will have to try it to see what I mean. You will get a lot of files if it is a large suite, but it is good granularity that you can use to pinpoint which row of your Grid caused the failure. A side effect of running from the command line is that you will have an audit trail of running the tests.
Regards,
Todd
