[SOLR-9107] add annotation for more fine grained control of SSL per test-class

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.1, 7.0
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 13/May/16 01:18
• Updated: 17/Jun/16 13:11
• Resolved: 08/Jun/16 18:45

Description

Spinning off this idea from my earlier comment in SOLR-5776...

---

At some point in the future, after all this soaks, we should consider increasing the odds of using SSL – perhaps even add a new annotation (or replace @SupressSSL) with a param to help control the odds of using SSL / clientAuth on a per-class basis, ie...

  @UseSSL(false) // same as @SupressSSL
  @UseSSL() //  same as default if no annotation: SolrTestCaseJ4 picks SSL / clientAuth using LuceneTestCase.rarely
  @UseSSL(ssl=0.75,clientAuth=0.25) // fine control of odds of using ssl & clientauth

...some tests, like TestSSLRandomization should ideally have much higher odds of using SSL then other tests, and if we had an easy way to say "these handful of simple cloud tests should use SSL very frequently" then it wouldn't matter so much if the odds of other really 'expensive' tests only use SSL once in a blue moon.

Issue Links

• relates to: SOLR-9182 Test OOMs when ssl + clientAuth
• relates to: LUCENE-7308 checkJavaDocs.py mis-chunks javadocs HTML and then wrongly reports imbalanced tags