[Me]:- Guruji, I was wondering how important logging is for automation.
[Guruji]:- Logging is imperative for the successful release of any product. It is required for ensuring that enough test cases are passing and release criteria is being met with. Without proper logging, there is no way of determining, if a component meets the QA needs as prescribed. The logging infrastructure has to be robust.
[Me]:- And what about error reporting?
[Guruji]:- Error reporting is one of the crucial aspects of logging required for test cases. Errors, Warnings and informational messages should be context sensitive and be able to point to the source of the problem in the test code. They should also be as much unique as possible so that a result from a wild card search should be able to point the test suite and the test Case the error message belongs to.
[Me]:- So, can you please summarize the Do’s and Don’t of logging.
[Guruji]:- ok
| Do’s | Don’ts: |
|
|
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
