[
https://issues.apache.org/jira/browse/LUCENE-8626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174997#comment-17174997
]
Dawid Weiss commented on LUCENE-8626:
-------------------------------------
bq. Still, without automated enforcement
For LuceneTestCase subclasses an automatic enforcement of this is trivial: add
a test rule (or before class hook) that checks test class name (it can go up
the chain of superclasses but doesn't have to). The benefit of doing this vs.
file name checks is that actual test suites would be verified - not any other
class that isn't a test suite.
It would also work across all projects. Including those that import
lucene-test-framework (which may be problematic for people?).
> standardise test class naming
> -----------------------------
>
> Key: LUCENE-8626
> URL: https://issues.apache.org/jira/browse/LUCENE-8626
> Project: Lucene - Core
> Issue Type: Test
> Reporter: Christine Poerschke
> Priority: Major
> Attachments: SOLR-12939.01.patch, SOLR-12939.02.patch,
> SOLR-12939.03.patch, SOLR-12939_hoss_validation_groovy_experiment.patch
>
>
> This was mentioned and proposed on the dev mailing list. Starting this ticket
> here to start to make it happen?
> History: This ticket was created as
> https://issues.apache.org/jira/browse/SOLR-12939 ticket and then got
> JIRA-moved to become https://issues.apache.org/jira/browse/LUCENE-8626 ticket.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
