You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2018/01/03 14:18:07 UTC

[GitHub] ivankelly commented on issue #930: [WIP] Issue #903: Bc tests based on docker

ivankelly commented on issue #930: [WIP] Issue #903: Bc tests based on docker
URL: https://github.com/apache/bookkeeper/pull/930#issuecomment-355022177
 
 
   @sijie @eolivelli 
   How about this approach? It uses a library called MavenClassLoader to pull all dependencies for each version into ClassLoader. Then the methods are called via reflection (I don't think there any other way).
   The backward proxy stuff is no longer needed.
   
   This is only needed for interop tests, where we need to check how ledgers from one version interact with ledgers from another version. Testing all client versions with the latest bookies should each have their own simpler tests.
   
   Do we actually state anywhere what our overarching compatibility guarantees are? 
   
   Re arquillian, I'm aware we want to use for integration tests and failure injection too. However, I'd like to see a PoC of how this would be done before settling with it, but so far it's been a pain to work with. Docker-java is wordy, but it follows the docker rest api, which is very well documented.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services