gerlowskija commented on PR #3023: URL: https://github.com/apache/solr/pull/3023#issuecomment-2583508494
@colvinco asked the following in a dev-thread related to this PR: > I've not really looked at the BATS tests before. [...] I take it I can just run > curl to poke each API. So they should be quick enough to write when I > get back to this next week. Is that the best option then? Or should I use > the RestTestBase and go that route instead? My two cents are that we'd be better sticking to a Java-based test here. BATS tests give you, in some senses, a bit more fidelity than a JUnit test since they're testing the same tgz or zip distribution that an end-user downloads, but that comes at a pretty steep cost: they're much much slower to run, can't be parallelized, aren't cross-platform, etc. So my suggestion would be to write in Java unless you run into a reason to do otherwise. That said - if you like the simplicity of BATS or think the extra fidelity is worth it, I'm OK with that too. This'll be a big boost to our v2 test coverage, so it'll be a huge win whichever approach you take. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
