This is great, if your user report has enough details for you to replicate the problem in a test case. More often than not, I spend a fair amount of time looki

This is great, if your user report has enough details for you to replicate the problem in a test case. More often than not, I spend a fair amount of time looking for error logs, tracing through the code, and generally getting a good sense of the exact parameters of the underlying issue. But yes, if you identify a defect that you can replicate, write a test for it so you can confirm that a) your fix actually works and b) you don't backslide in the future.