From: Egon W. <el...@ca...> - 2003-03-12 09:17:59
|
On Wednesday 12 March 2003 6:29 am, Edgar Luttmann wrote: > >>I don't want to duplicate the code of the test classes just to get some > >>classes which produce graphical debug output. > >>Of course, there might well be some tests where the graphical output > >>*itself* is tested. These should go into a special suite. > > > > That's what I intend to have the cdk.test.GraphicalCDKTests.java for... > > Do you really mean that? I think there is still a difference between the > case where you just use some graphical output for testing (imagine the > drawing of some image). And cases where there might be some part of GUI > which needs to be tested in regards of it doing what it is supposed to > do. For example hitting a certain button disables some other controls. Ah. Interesting point. I was not refering to GUI testing... I know that there are some tools to do this automatiacally (also for Java?), but I've never looked at them... What I meant, was the graphical output used for example for checking wether aromaticity is detected using the MoleculeViewer... > This latter case is GUI logic which needs to be checked, and the first > mentioned case I think is not so easy to handle automatically. I agree. Do you have experience with the former (GUI logic cecking)? Can you tell me a bit about that? Egon |