[
https://issues.apache.org/jira/browse/SOLR-15925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17476251#comment-17476251
]
Uwe Schindler commented on SOLR-15925:
--------------------------------------
Hi,
I think you can't set different deafaults for test and check, because "check"
only depends on "test". A "hack" would be to check Gradle's command line for
"check" and oly then enable some properties. But this is all not very well
designed and may break.
I am not sure if annotations are inherited, but one can do the check in an
inherited way. We may just need to do the superclass iteration in
SolrTestCaseJ4.
By the way: We may not even need an annotation. If all integration tests have
the same superclass, we can just place the check in the constructor and stop
executing it.
> @Integration annotation and -Ptests.integration=false flag
> ----------------------------------------------------------
>
> Key: SOLR-15925
> URL: https://issues.apache.org/jira/browse/SOLR-15925
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build, Tests
> Reporter: Jan Høydahl
> Priority: Major
>
> Ref dev mail thread
> [https://lists.apache.org/thread/lgnz0jroqr40x876ocdzz9ft47vmo24v] we need a
> way to run ONLY unit tests, i.e. skip all tests spinning up clusters etc.
> Suggestion is an {{@Integration}} annotation for those tests (are they
> inherited, then it's enough to put on some base classes), and a gradle
> filtering param {{-Ptests.integration=false}}
> Next, the question is what should be the default for {{gradlew test}} and
> {{gradlew check}} ??
> [~uschindler]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
