Re: [development] selenium test

Robert Douglass wrote:

And since we have our own handling, couldn't we just have a debug_backtrace() sitting in there, and perhaps an extra mode on the error handling settings that lets errors or warnings do a backtrace?

I have implemented such things in the form of debug_assert() on sites we're working on. One example is checking that node_load() is called with a valid argument. If not, a backtrace is far more helpful than an error within node_load(). I do clean up the backtrace to only show the essentials and the top few items in the stack. I really don't care to see everything all the way down to the bootstrap process.