SE still has some affinity for test methods named testSomethingOrOther. In the following example, you can debug 'testOne' from the unit testing window, but you cannot do the same for 'twoTest', SE complains that it cannot execute a test for which it has no source file.
@Test
public void testOne(){
}
@Test
public void twoTest() {
}
On a side note: The unit testing window is weak instrument to run tests from. Ideally it should build and show a tree of all the unit tests in the project. Instead it just shows test(s) you last ran and never updates for tests run in the debugger. Every mistake when trying to run a test wipes out the tests tree. This happens more often than you might think because the SE unit testing framework is highly dependent on an accurate tag file, so after adding new tests it is often necessary to rebuild the project tags before being able to run them. Furthermore SE should add support for testNG.
