Test automation related content

As subject says... added a bit more granularity to the checks.
I think it should usually be in the stack trace isn't it?  maybe less clear though - mind you I have done some evil stuff editing stack traces before but I'm not sure it's good practice.  Another trick is to use the SecurityContext to find the names of the classes on the stack, that works reliably and I've used it for loggers before.