[
https://issues.apache.org/jira/browse/SOLR-9632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568746#comment-15568746
]
Alan Woodward commented on SOLR-9632:
-------------------------------------
>From the mailing list, re SOLR-9132:
[~hossman] wrote:
It's not immediately obvious to me why these collection deletions can't be
done in an @After method -- but if they need to live in each test method
can we at least have an @After method that asserts no collections exist
(via a STATUS call) so if someone writes a new test method but forgets to
delete that collection then the @After method will catch it and give them
a self explanatory failure instead of some future confusing/trappy error
that depends on test order or what not?
[~romseygeek] wrote:
They all have different collection names, which is why we can’t do it in an
@After method, but you’re right, it is trappy. How about instead we add a
.deleteAllCollections() command to MiniSolrCloudCluster, which will ensure that
each test starts up in an empty cluster?
> Add a deleteAllCollections() method to MiniSolrCloudCluster
> -----------------------------------------------------------
>
> Key: SOLR-9632
> URL: https://issues.apache.org/jira/browse/SOLR-9632
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Alan Woodward
> Assignee: Alan Woodward
>
> This would make test tearDown easier in lots of places.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
