I created a few JIRAs to spike "bin/solr" tests several years back (SOLR-11749). I didn't have quite enough time to get it across the finish line previously but I think it's a great idea to have tests of this sort. At the time I was writing tests in bash - but realized that wasn't a particularly scalable approach.
Would be happy to help where I can if the effort gets restarted. Best, Jason On Mon, Sep 7, 2020 at 3:14 AM Uwe Schindler <u...@thetaphi.de> wrote: > It should be part of an integration test suite, only on module "package" > after assembly. That's something to setup. Please make sure that it works > with any operating system, 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 > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > -----Original Message----- > > From: Dawid Weiss <dawid.we...@gmail.com> > > Sent: Monday, September 7, 2020 9:00 AM > > To: Lucene Dev <dev@lucene.apache.org> > > Subject: Re: Tests that use bin/solr? > > > > 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 <dsmi...@apache.org> wrote: > > > > > > 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 nice tests in SolrExampleTests which is a base > class and > > many implementations that create SolrJ clients in different ways. I > could > > imagine modifying this such that if a magic system property is specified > to a > > URL of an existing Solr instance, then the test would not create a > > JettySolrRunner but instead use the configured one. This would then be > > executed by the smoke tester and maybe a future Docker release process. > I > > have test infrastructure I wrote where I work that does this sort of > thing for our > > Solr plugins, and it works great. > > > > > > ~ David Smiley > > > Apache Lucene/Solr Search Developer > > > http://www.linkedin.com/in/davidwsmiley > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
