6 Best Practices for Tracing & Logging in Test Automation – SIP Series
Since test automation scripts would run in most of the cases in scheduled mode unsupervised without any manual intervention, it becomes imperative to have solid tracing and logging mechanisms built into the automation framework so that if anything goes wrong, it is still possible to recreate the error and make meaningful logical inferences about the source of the error.
The Long Story
All remains well when nothing goes wrong. But that unfortunately is not the case in real world. In real world, disks get full, memory becomes corrupt, file-handles become invalid, power goes off – in short – so many things which “should