Hi, I think the point why such tests are unit tests is because those tests do not require a running Stanbol instance. At the moment integration-tests are executed against a running Stanbol server. But what should we do with tests that access external resources but do not need Stanbol?
Maybe, we could mark those unit tests that access external resources with some annotation that says: This unit test accesses an online resource. Via some switch all those tests could be disabled if desired. Best, - Fabian 2012/9/25 Bertrand Delacretaz <[email protected]>: > On Tue, Sep 25, 2012 at 10:09 AM, Fabian Christ > <[email protected]> wrote: >> ...why not handle all unit tests that access external services as >> integration-tests? IMHO these are no unit tests anymore if they access >> an external resource. So migrating them to integration-tests would be >> solution.... > > +1, having unit tests that timeout on connections or fail silently > because an external service is not there is not good. > > Maybe we need three types of tests: > 1) Unit tests - quick, no external connections > 2) Integration tests in offline mode > 3) Integration tests in online mode, activated by a Maven profile or > -Dproperty > > -Bertrand -- Fabian http://twitter.com/fctwitt
