[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Clustering tests and hsqldb

[ovidiu.feodorov@jboss.com]

Tim wrote : For now though, could everyone ensure they run the clustering-tests target before committing after they run the normal test suite? Thanks 

Why don't you add the clustering-tests target to "tests"?

Also, you can configure the default database on a test-by-test basis, by overriding the value of  < property name="functional.tests.database" value="hsqldb" />. Override it when you call  < antcall target="clustering-tests"/>

Scott wrote : 
  | What about just switching to another embedded database such as derby or javadb?
  | 

We can do that, but I have one question and one observation related to this.

The question is why JBoss AS doesn't use derby or javadb instead of hsqldb?

The observation is that the value of the database a certain tests runs in top of can be changed on a test-by-test basis, so by just having an MySQL instance in stand by and configuring the tests to run with "mysql" would be sufficient. We already need MySQL for stress tests, so this would be the simplest way to get address the problem.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982847#3982847

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982847