测试用Java Swing编码的应用程序GUI：最佳方法？

Question

I have to automatically generate test for a Java "drawing" application GUI (like ArgoUML/LaTeXDraw/etc). I need to verify that the tested application behave correctly. In my given example, I need to check that the Undo/Redo buttons works well = Undo put the canvas in the predecessing state and Redo put it again in the state it used to be.

I have already an idea of how I will approach the problem but I would like feedback of experienced people:

• Should I use the Robot class to simulate the inputs onto the GUI? Or is there an easier way?

• I need to capture the state of the program for later analysis to see if the state of the program is consistent, should I just screenshot the window or is there a way to iterate through all the JFrame's components and capture their properties (it should include canvas state)?

• More importantly, I do not know how to locate each button on the interface. What is the simplest way to tell the Robot that a given button is at a certain (x, y) position in the window? Should I search the pixels in a .jpeg version of the button? Should I locate each button on the interface manually (ie create a class for each button containing x, y attributes)?

• And finally, I have never "attached" a Robot to a given program. Can I just load the .jar file of the software I want to test and tell Robot to operate on that window? Or do I need to work with all the source files from the original project?

Thank you for your time, if any part of my question seems not clear enough please tell me and I will try to explain it even more clearly.

PS: any advice concerning the work I need to do is welcome :)

Answer 1

I've done what you've explained in the comment to the other answer.

Robot can be useful for various parts of the process but, depending on how it was written, the desire to follow best testing practices, and overall needs it can get limited quick. If you didn't write it or best coding practices keep you from getting access to or directly testing aspects of the application then other means are necessary.

My experience led me to tunnel down the main entry point using reflection to test the actual state (like text values of various components). Robot was only useful for my case to perform key events .

Ultimately, the answer(s) depend on many factors:

1. Robot? - Sure, use it as far as it suits your needs.
2. Do what's easiest while still meeting the requirements. If a screen shot will do, do it (with Robot ). If you need more information you can get the components of a JFrame or JPanel and save what ever properties offered.
3. This can be done a number of ways though investigation of the UI. Finding the button and doing doClick directly on it, moving the mouse with Robot and doing a mouse press, etc.
4. When you instantiate a new Robot it will be linked to the main device. Nothing more is needed in simple scenarios than new Robot().keyPress(KeyEvent.VK_ENTER);

Given all that, there are pitfalls like focus. It's best to start your simulation/test and not touch any peripheral of the machine. Also, depending on the running time of some methods you may want to Thread.sleep() (as we regrettably did) or use joined threads.

Answer 2

You did not add any code so I can just guess:

If your code follows the MV(V)C pattern you don't need to test though the GUI. You can directly test the controller methods that handle the redo/undo and verify that they correctly change the model and communicate with the undo/redo stack (is is part of the model in my world...).