we don't need to extend the timeout value. We need to get the stacktrace 
written into some log-file _before_ the test is killed by the timeout.

Usually the fact of some test is timed out mean some hang up or even a 
deadlock occurred, so we need to determine the reason of such a problem 
and as such we need to have a stacktrace logged somehow.

So, we are finding a way to run something like 'jstack -F <PID> | tee 
<test>/target/work/data/.metadata/jstack.log' or something like this 
_right_before_ the test will be killed by surefire as timed out.