# Looking for ElasticSearch client developers & integration test suites **URL:** \ **Category:** Elasticsearch\ **Created:** [September 26, 2012, 9:57pm UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165 "2012-09-26T21:57:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Nick\_Zadrozny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick_zadrozny/32/1150_2.png) [@Nick\_Zadrozny](https://discuss.elastic.co/u/Nick_Zadrozny)\ **Post date:** [September 26, 2012, 9:57pm UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/1 "2012-09-26T21:57:54Z")
Hi all, I'm in the process of building a hosted ElasticSearch service, to be available first as a Heroku addon, and eventually for other platforms as well. One of the last things I'm working on before we launch for real is to gather and run a bunch of test suites against our systems. I want to make sure we're solidly compatible with as wide a range of clients and use cases as possible. So if you've built an ElasticSearch client, or have any kind of ElasticSearch integration test suite laying around, I'd love to add that to my collection. Lately I've been developing against Tire's integration tests, which has been helpful. I've also collected a few other projects that I've found hosted on GitHub, particularly those that are set up to run on Travis CI. That said, I'm mostly a Ruby guy, so I may have some questions for the authors or contributors: notably, how to configure the test suite to run against an arbitrary URL. So if you're an ElasticSearch client author — or really any ES user — interested in making sure we're maximally compatible with their client of choice, I'd love to borrow a few minutes of your time to get up to speed with your tests. Also, if you have any questions about our service — particularly if you're using us in beta already — feel free to ask! Happy to talk shop about what we're up to. (Maybe you're wondering why I need all these tests?) -- Nick Zadrozny Cofounder, One More Cloud [websolr.com](http://websolr.com) [https://websolr.com/home](https://websolr.com/home) • [bonsai.io](http://bonsai.io) [http://bonsai.io/home](http://bonsai.io/home) Hassle-free hosted full-text search, powered by Apache Solr and ElasticSearch. -- ---
**Author:** ![Raffaele\_Sena](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raffaele_sena/32/1759_2.png) [@Raffaele\_Sena](https://discuss.elastic.co/u/Raffaele_Sena)\ **Post date:** [September 26, 2012, 10:27pm UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/2 "2012-09-26T22:27:23Z")
Hi Nick, I have worked with Tire on a couple of projects (and it is right now my favorite client library). I have also used a PHP client for a very basic search application (didn't want to do a full rails installation so I wanted something I could use with just Apache running): [http://netflix.aromatic.com/](http://netflix.aromatic.com/) Also, I recently did this [[GitHub - raff/elseql: a SQL-like command line client for elasticsearch](https://github.com/raff/elseql) ] in python (I am forced to work in python these days and I found a quick and dirty SQL parser). The main reason for a "SQL-like" command line client is to run reports on data I have stored only in Elasticsearch. And I was tired to write a ruby/tire app every time I had to do a slightly different query 🙂 -- Raffaele On Wed, Sep 26, 2012 at 2:57 PM, Nick Zadrozny [nick@onemorecloud.com](mailto:nick@onemorecloud.com) wrote: > Hi all, > > I'm in the process of building a hosted Elasticsearch service, to be > available first as a Heroku addon, and eventually for other platforms as > well. > > One of the last things I'm working on before we launch for real is to gather > and run a bunch of test suites against our systems. I want to make sure > we're solidly compatible with as wide a range of clients and use cases as > possible. > > So if you've built an Elasticsearch client, or have any kind of > Elasticsearch integration test suite laying around, I'd love to add that to > my collection. > > Lately I've been developing against Tire's integration tests, which has been > helpful. I've also collected a few other projects that I've found hosted on > GitHub, particularly those that are set up to run on Travis CI. That said, > I'm mostly a Ruby guy, so I may have some questions for the authors or > contributors: notably, how to configure the test suite to run against an > arbitrary URL. > > So if you're an Elasticsearch client author — or really any ES user — > interested in making sure we're maximally compatible with their client of > choice, I'd love to borrow a few minutes of your time to get up to speed > with your tests. > > Also, if you have any questions about our service — particularly if you're > using us in beta already — feel free to ask! Happy to talk shop about what > we're up to. (Maybe you're wondering why I need all these tests?) > > -- > Nick Zadrozny > > Cofounder, One More Cloud > > [websolr.com](http://websolr.com) • [bonsai.io](http://bonsai.io) > > Hassle-free hosted full-text search, > powered by Apache Solr and Elasticsearch. > > -- -- ---
**Author:** ![Michael\_Klishin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_klishin/32/1062_2.png) [@Michael\_Klishin](https://discuss.elastic.co/u/Michael_Klishin)\ **Post date:** [September 26, 2012, 11:03pm UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/3 "2012-09-26T23:03:51Z")
2012/9/27 Nick Zadrozny [nick@onemorecloud.com](mailto:nick@onemorecloud.com) > So if you're an Elasticsearch client author — or really any ES user — > interested in making sure we're maximally compatible with their client of > choice, I'd love to borrow a few minutes of your time to get up to speed > with your tests. Nick, I am the author of Elastisch ([http://clojureelasticsearch.info](http://clojureelasticsearch.info)). To run our test suite against a URL: 1. Make sure you have JDK installed (6 or 7, Oracle, OpenJDK or Apple, they all will work equally well) 2. Install Leiningen: [Leiningen](http://leiningen.org/#install) 3. Export ELASTICSEARCH\_URL 4. Follow instructions in the README: [GitHub - clojurewerkz/elastisch: A minimalistic Clojure client for ElasticSearch, supports both HTTP and native transports](https://github.com/clojurewerkz/elastisch#development) It will download all dependencies and run tests 3 times (against 3 Clojure versions), each taking ~35 seconds on a pretty dated machine. Note that ELASTICSEARCH\_URL will only be used in master. If your service will be primarily available to heroku users, it may be a good idea for us to backport this to 1.0.x. ## HTH, MK > **[michaelklishin - Overview](https://github.com/michaelklishin)** > > Infrastructure, data services, distributed systems, Erlang, Elixir, Rust - michaelklishin [http://twitter.com/michaelklishin](http://twitter.com/michaelklishin) -- ---
**Author:** ![Nick\_Zadrozny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick_zadrozny/32/1150_2.png) [@Nick\_Zadrozny](https://discuss.elastic.co/u/Nick_Zadrozny)\ **Post date:** [September 28, 2012, 8:48pm UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/4 "2012-09-28T20:48:38Z")
Thanks, Michael! All that was very helpful. On Wed, Sep 26, 2012 at 4:03 PM, Michael Klishin \< [michael.s.klishin@gmail.com](mailto:michael.s.klishin@gmail.com)\> wrote: > Note that ELASTICSEARCH\_URL will only be used in master. If your service > will be primarily available > to heroku users, it may be a good idea for us to backport this to 1.0.x. Environment variable support is an interesting one. Heroku addons must prefix their environment variables with their uppercased addon name, so nobody will be setting an ELASTICSEARCH\_URL variable. At least, for now. That puts the onus on setup documentation to show the user how to set the URL from whatever environment variable we do supply. So backporting may or may not be necessary, depending on how straightforward it is for the user to fetch the URL from some other environment variable in their app. I see that Elastisch has its own mailing list, so maybe I'll follow up with you there if I have more questions about that… -- Nick Zadrozny Cofounder, One More Cloud [websolr.com](http://websolr.com) [https://websolr.com/home](https://websolr.com/home) • [bonsai.io](http://bonsai.io) [http://bonsai.io/home](http://bonsai.io/home) Hassle-free hosted full-text search, powered by Apache Solr and Elasticsearch. -- ---
**Author:** ![Dan\_Fairs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_fairs/32/1205_2.png) [@Dan\_Fairs](https://discuss.elastic.co/u/Dan_Fairs)\ **Post date:** [September 29, 2012, 8:48am UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/5 "2012-09-29T08:48:00Z")
Hi Nick, > So if you're an Elasticsearch client author — or really any ES user — interested in making sure we're maximally compatible with their client of choice, I'd love to borrow a few minutes of your time to get up to speed with your tests. The Python library pyes has a test suite you could use: [GitHub - aparo/pyes: Python connector for ElasticSearch - the pythonic way to use ElasticSearch](https://github.com/aparo/pyes) I'd also be happy to run our application's fairly extensive test suite against your hosted platform. Is there any way that could be arranged? Note that some of our tests require a native script - happy to provide the jar if that's something that can be arranged. If not, well, those integration tests will fail, but the rest of the suite should pass! ## Cheers, Dan Dan Fairs | [dan.fairs@gmail.com](mailto:dan.fairs@gmail.com) | @danfairs | [secondsync.com](http://secondsync.com) -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:10am UTC](https://discuss.elastic.co/t/looking-for-elasticsearch-client-developers-integration-test-suites/9165/6 "2017-07-06T03:10:47Z")