I've put together a guide about how to test distributed software applications.
Well, first news is that I'm trying to get this web site up and going. Despite the fact that I want to keep it text only, organizing and maintaining it is not an easy task. A good friend of mine - Catalin Rotaru - is trying to build a framework to help with automated web site publication and maintenance. Once he's framework will reach a usable form, I'll probably give it a try, see if it solves at least a few of my problems. Catalin is sharing his experience online as he's moving forward with his work. If you're interested in monitoring his progress have a look at thexmlsite.com.
More news it that I've started to work on JUnit compatibility. The kind of compatibility I'm working on is not for TESTARE to execute JUnit tests, but more to allow JUnit test suite runners to discover and execute TESTARE tests, and this without touching JUnit itself. It is doable, but I not sure if I can obtain full functionality in this compatibility mode. The main problem is related to the execution of global fixtures. I would need a JUnit to notify me before the first test in the suite is execute it, but that's impossible. Hmmm..... I think I'll write a blog entry about what JUnit could do in order to make life easier for people writing extensions. I would like to implement the same kind of compatibility for other mainstream java testing frameworks, such as TestNG or JTiger. Problem is I'm not at all familiar with the internal details of these tools, so I'll probably need some time to figure it all out.