[
https://issues.apache.org/jira/browse/STANBOL-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163378#comment-13163378
]
Rupert Westenthaler commented on STANBOL-400:
---------------------------------------------
All solr related unit tests do not delete artifacts after completion to allow
the inspection of results after the completion of the tests. If needed such
tests could manually delete the artifacts of previous executions in the
@BeforeClass state.
Regarding: "... those tests look a bit like integration tests not unit tests."
The "ManagedSolrServerTest" tests the standalone implementation of the
ManagedSolrServer. This is the implementation used when running outside an OSGI
environment. The OSGI version is implicitly tested by the initialization of the
full launcher - because it is used to initialize the dbpedia referenced site.
> Solr- failing test when running Maven without clean
> ---------------------------------------------------
>
> Key: STANBOL-400
> URL: https://issues.apache.org/jira/browse/STANBOL-400
> Project: Stanbol
> Issue Type: Bug
> Components: Commons
> Environment: Ubuntu Linux, Java 1.6 64Bit
> Reporter: Fabian Christ
> Labels: Test
>
> In commons/solr/managed run
> $ mvn clean install -> SUCCESS
> $ mvn install -> FAILURE
> Tests in error:
> org.apache.stanbol.commons.solr.managed.ManagedSolrServerTest: Can not
> create core with name 'entityhub' because a Core with that name does already
> exist!
> Seems as if this test is not stateless. I don't had a deeper look but those
> tests look a bit like integration tests not unit tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
