I had some batch of Junit tests that were taking close to 20 minutes and it was wasteful to wait everytime before checking in code, one trick I found was to use the forkmod="once" property. Using this reduce the time to 5 minute 8 sec.
Earlier Junit was forking a JVM per test and now its doing one for all test so its very fast. Here is some documentation from Junit on this property.
Controls how many Java Virtual Machines get
created if you want to fork some tests. Possible values are
"perTest" (the default), "perBatch" and
"once". "once" creates only a single Java VM
for all tests while "perTest" creates a new VM for each
TestCase class. "perBatch" creat…
A trick to test selenium with ExtJS is to use cssSelectors. As an element can have more than one css classes and you really dont need to define any style for that css class it can be a good locator for the element and faster than XPATH on IE.
You can define cssSelector as
ctCls: 't-btn-yellow x-btn-over',
iconCls: 't-send seleniumSendNote',
and you can then in your test call the button click as
String notes = "This is a test note from selenium";
+ notes + "')");