Hi all, I have been experiencing problems when using embedded software (HBase, Cassandra) in unit tests. My main itches are:
1) Dependencies incompatibilities (e.g. Guava). Now this could be considered a blocker: https://issues.apache.org/jira/browse/FLUME-2286 2) Cross-polluting the classpath for both Flume and the embedded server. When pulling a big project like HBase or Cassandra to the test classpath, we're testing an environment that is different from both Flume's and the embedded software. This can create test bugs and, what is worse, mask bugs that won't show up in test but will show up in production. 3) Testing different versions of HBase or Cassandra aggravates the problem. What do you think about moving these tests to integration-test (with JUnit to keep it simple) and set them up to use external instances of required services? Best, -- Santiago M. Mola <http://www.stratio.com/> Avenida de Europa, 26. Ática 5. 3ª Planta 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 352 59 42 // *@stratiobd <https://twitter.com/StratioBD>*
