stem, because we are leaving Java world here (and
>>> because of this, don't mix that into default unit tests).
>>>
>>> Currently we have a test for bin/solr: Smoketester
>>>
>>> Uwe
>>>
>>> -
>>> Uwe Schindler
>>&
ault unit tests).
>>
>> Currently we have a test for bin/solr: Smoketester
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> Achterdiek 19, D-28357 Bremen
>> https://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> > -Original Messag
19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Dawid Weiss
> > Sent: Monday, September 7, 2020 9:00 AM
> > To: Lucene Dev
> > Subject: Re: Tests that use bin/solr?
> >
> > Just
ly we have a test for bin/solr: Smoketester
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss
> Sent: Monday, September 7, 2020 9:00 AM
> To: Lucene Dev
> Subject: Re: Tests tha
+1
This should be used to write tests for rolling upgrades across different
versions.
On Mon, 7 Sep, 2020, 12:30 pm Dawid Weiss, wrote:
> Just a note - such integration tests should depend on (and consume)
> the output of solr/packaging (a ZIP file with fully assembled
> package). Then you're
Just a note - such integration tests should depend on (and consume)
the output of solr/packaging (a ZIP file with fully assembled
package). Then you're really sure you're testing the final artifact.
Dawid
On Mon, Sep 7, 2020 at 7:51 AM David Smiley wrote:
>
> Do we have any tests that operate
Do we have any tests that operate on a "real" Solr instance running from
"bin/solr"? Such tests could find problems with bin/solr and any classpath
matters in how Jetty operates. Solr does have JettySolrRunner which is
great but doesn't cover the aforementioned matters.
We've got some really
