Hi Thanks for suggestions, will check these *Thanks & Regards,* *Uday Kumar* *Product Search Tech*
On Fri, Jul 11, 2025, 14:08 Matthias Krüger < mkrue...@opensourceconnections.com> wrote: > Two options: > * For integration tests that use Solr "externally" start a Solr Docker > container using TestContainers (e.g. > > https://opensourceconnections.com/blog/2021/03/01/adding-integration-tests-to-a-solr-plugin-project/ > ) > * For integration tests that need to spin up SolrCloud but also need to > have access to Solr internals write a SolrCloudTestCase (e.g. > > https://github.com/apache/solr/blob/main/solr/solr-ref-guide/modules/indexing-guide/examples/IndexingNestedDocuments.java > ) > > > On Fri, Jul 11, 2025 at 10:19 AM Uday Kumar <uday.p...@indiamart.com > .invalid> > wrote: > > > Hi all, > > > > Currently, we run Solr on a test server and use it during our integration > > tests for Spring Batch Jobs. This server needs to be maintained and > > make sure solr is up and running while executing test cases. For the > > database connections, we use H2 in-memory DB, which works well because > it's > > fast and doesn’t need a separate server. > > > > We would like to know if there’s any standard practice to spin up > in-memory > > solr— so we don’t have to rely on a separate Solr server during tests. > > > > *fyi* > > > > *versions used in production:Java: 1.8* > > > > *Solr Cloud: v9.6* > > *Thanks & Regards,* > > *Uday Kumar* > > *Product Search Tech* > > >
