epugh commented on PR #1681:
URL: https://github.com/apache/solr/pull/1681#issuecomment-1785810470

   > > Up to this point I kindof thought the BATS framework was targeting bash 
specifically, but you two are the most familiar so if you think it'd be a 
decent fit I'm happy to give it a shot...
   > 
   > Yeah, there is a niceness about just using bash in the BATS framework, and 
I'm not sure any of the curl stuff is that bad... I can definitely see some 
awesome integration tests using python, but that would target other stuff maybe?
   
   
   
   > > Up to this point I kindof thought the BATS framework was targeting bash 
specifically, but you two are the most familiar so if you think it'd be a 
decent fit I'm happy to give it a shot...
   > 
   > Yeah, there is a niceness about just using bash in the BATS framework, and 
I'm not sure any of the curl stuff is that bad... I can definitely see some 
awesome integration tests using python, but that would target other stuff maybe?
   
   I could see a whole separate set of tests that demonstrate complex multi 
step processes (and are probably going to end up being brittle ;-( ) that we 
could add.  For example, I added a .bats test that demonstrated running two 
SEPARATE SolrCloud instances, and using classic Replication to move data 
between them ;-).   There are lots of things like splitting collections or 
using the REINDEXCOLLECTION command that might benefit by a separate 
"integration" test approach both to validate the code works, but also to show 
folks how to do these things.   Heck, #1999 features a complex multi step bats 
test just to help me figure out how it would all work together ;-).


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to