Test timeout support about dbfit HOT 3 OPEN

The desired behaviour is the given test to be aborted if a query takes too long.

I believe that you could achieve the same effect in other ways even without such a feature in DbFit:

1. Configure a timeout for long queries at the database level
2. Configure your CI to break off the test run if something takes too long (obviously not ideal as that prevents subsequent tests from running, but at least prevents the build from hanging)
3. You could in fact use the JUnit feature you mentioned, because FitNesse (and hence DbFit) tests can be triggered using JUnit. This is in fact how DbFit's own acceptance tests are run inside the Maven build.

Would any of these alternatives work for you?

Also, adding stable and well-running timeout functionality is a non-trivial task technically, one that could potentially add quite a bit of complexity to the code. It's not that I'm not ruling out adding this feature, I just don't see getting to it any time soon.

I would be open to pull requests though!

from dbfit.

There is a [Statement.setQueryTimeout](http://docs.oracle.com/javase/7/docs/api/java/sql/Statement.html#setQueryTimeout(int\)) method which may be helpful in implementing this.

No urgent need for this from my side. Maybe I'll take the opportunity for pull requests for some of the open issues - as soon as I get some idea about the internals of dbfit, fitness and all the related stuff :-)

from dbfit.

There is a Statement.setQueryTimeout method which may be helpful in implementing this.

Ah, didn't know about this - makes things pretty simple!

No urgent need for this from my side. Maybe I'll take the opportunity for pull requests for some of the open issues - as soon as I get some idea about the internals of dbfit, fitness and all the related stuff :-)

That would of course be awesome and very appreciated! Give me a heads-up if a particular bug/features takes your fancy and I can support you with it...

from dbfit.