Hi there, while having dinner I had a great idea: IMO it would be ubercool to have Mauve support Beanshell scripts as testcases. I came to this idea because I have nearly completely switched to using BeanShell for quick and dirty testing, and my motivation to turn all those little tests into Mauve testcases is not too high (sorry). I could imagine to just drop .bsh scripts into the Mauve directories side-by-side with the .java files, and have a special Mauve test harness that loads such bsh script into a BeanShell environment. This BeanShell environment should have a new function (or a couple of overloaded functions) like check() that replaces the TestHarness.check() methods. Such an approach has some interesting benefits: 1. much faster test development. using bsh scripts, we could literally place code snippets from the bug database or whereever into Mauve and create testcases with minimum effort 2. using setAccessibility(true), we could test methods/fields that are otherwise not accessible (protected, default and private methods and fields), which would be extremely useful. Look at how we test all the protected methods and classes in Swing, and you know what I mean. Simply accessing such stuff directly would decrease the LOC dramatically I'm sure there are more benefits, but only these two seem very appealing to me. Tony, you are currently working with Mauve, what do you think about this? And what do the others think about this? Cheers, Roman -- ?Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.? - William Blake -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: Dies ist ein digital signierter Nachrichtenteil Url : http://developer.classpath.org/pipermail/classpath/attachments/20060405/83f9e738/attachment.pgp
