My company is currently evaluating TrackRecord. If we were to decide against using it, and QADirector for that matter, what options could I experiment with for error logging in QA Run? Currently, my only idea is to Write an error message for a failed script to a seperate file, and extract it into a bug tracker? Do any of you QA Run users not use QADirector and have a simular issue? What did you do to resolve it? Thanks.
QARuns and QADirectors logging features both suck. It's such a pain to look through all those QARun logs and QADirector logs when you ran a ton of tests over night.
I have an Oracle database with test cases. All my QARun scripts write the results of the test cases to the database. We also created a front end for the database so we can enter test cases and view results. This is also great for running reports in crystal reports, perl, or any other reporting tool.
"If your not part of the solution, there's good money to be made in prolonging the problem."