In that case is even easier, you can use the Cargo maven plugin and failsafe.
This is an example [1] but the point is: - configure Cargo to start a container (e.g. jetty, tomcat) with Solr deployed, in the pre-integration-test phase - execute any *IT test case class - stop the container in the post-integration-phase Let me know if you need further help Best, Andrea [1] https://github.com/agazzarini/SolRDF/blob/solrdf-1.0/solrdf/solrdf-integration-tests/pom.xml On 10 Dec 2015 06:22, "Sathyakumar Seshachalam" < sathyakumar_seshacha...@trimble.com> wrote: > Hello Andrea, > > Thanks for the link. Am running 4.10.3. However the test-framework classes > haven¹t changed much. I will give this a try. > > > On 09/12/15, 4:11 PM, "Andrea Gazzarini" <a.gazzar...@gmail.com> wrote: > > >Hi Sathyakumar, > >check this post [1] (assuming you're using Solr 5.x), maybe it can help. > > > >Andrea > > > >[1] > > > http://andreagazzarini.blogspot.it/2015/10/how-to-do-integration-tests-wit > >h-solr.html > > > >2015-12-09 11:32 GMT+01:00 Sathyakumar Seshachalam < > >sathyakumar_seshacha...@trimble.com>: > > > >> Are there any documentations around Solr test framework. ( > >> http://mvnrepository.com/artifact/org.apache.solr/solr-test-framework) > >> > >> I am looking to do integration tests to just check if I am able to add > >> document and search it via JUnitTests. There does seem to be a > >> test-framework from solr, but the documentation seems to be woefully > >> inadequate. > >> In my case I have a conf folder that contains the schema and solrconfig > >> (that I will actually copy to my solr home and run in production), Just > >> with these two files in a folder, Is it possible to run an Integration > >>Test > >> ? > >> > >> Any pointers/suggestions ? I tried running test case pointing it to the > >> parent folder but got an error > >> > >> java.lang.AssertionError: fix your classpath to have tests-framework.jar > >> before lucene-core.jar > >> > >> And I cannot seem to fix the above either. Am using gradle and actually > >>do > >> have test-framework as the first dependency. > >> > >> > >> > >
