Default timeout value should be configurable

[Marc Tardif]

There should be a way to configure the default timeout value somehow instead of hard coding 60 seconds in the question class. Another approach might also be to configure a multiplier for timeouts because some machines are implicitly slower than others, such as virtual machines for example.

[Marc Tardif (cr3)]

This has been fixed by setting the default timeout from 60 seconds to nothing. The motivation is that this default is totally arbitrary and has been known to cause more confusion than anything else. Instead, it is possible to set the timeout in the test definition contained within a suites file.