I have a large set of tests that are executed using TestExecute. The test team are now stringing several test runs together, which makes the MHT log file very large. I am looking at ways to reduce th...
I have a Script Extension for logging (it's just a TXT file so easy to handle). A Script Extension for reading in test data + outputting results. And a Script Extension for various common control functions which are application agnostic like dealing with services, file + folder handling, etc etc. Another one for TFS integration. And a "driver" framework script unit which I can move from project to project.
Each project/application then just needs it's own name map and functions specific to it.
I prefer my own log simply as it gives me full control over it and how granular it is. I use global variables as control flags to switch parts of it on and off. And I can start and stop logs as I please - which I do.
Kind of similar to how logging in Python works if you are familiar with that?
I tend to only use the built in logs for debugging when I'm building stuff. Once I hand new test functions off to the main test teams, they use my logs which give them more application specific errors. Code errors will also be caught and put in there, but will be marked as such and handed back to me. Most tend to be application and data problems by the time the test guys are using them. Shouldn't be any/many code errors happening by the time I hand them off.