Thread: [Java-gnome-developer] Status update (and a question)
Brought to you by:
afcowie
From: Jeff M. <ku...@gm...> - 2005-01-07 13:50:28
|
Just wanted to let everybody know how java-gnome development is going. We are three days away from our 2.9.4 release which marks our API freeze for this development cycle. There have been a great many enhancements during this time and the development team is quite excited about the release. A few of the major enhancements are: * support for 64-bit platforms (if you have access to one please help test this!) * full support for gdk-pixbuf * major enhancements to the gdk bindings * major GObject enhancements * support for all new gtk widgets For a complete list of all enhancements please see the NEWS file for each of the packages. And now on to the question. During our next development cycle we hope to introduce a testing framework for the java-gnome bindings. The question is "should this testing framework be based on JUnit or Mauve?". I am interested in your experience with both of these tools. Thanks -- Jeffrey Morgan "The highest reward for a man's toil is not what he gets for it, but what he becomes by it" - Jon Ruskin |
From: Andrew C. <an...@op...> - 2005-01-07 14:10:11
|
On Fri, 2005-07-01 at 08:50 -0500, Jeff Morgan wrote: > And now on to the question. During our next development cycle we hope to > introduce a testing framework for the java-gnome bindings. The question = is > "should this testing framework be based on JUnit or Mauve?". I am intere= sted > in your experience with both of these tools. [cut and paste from #java-gnome] Unit testing GUI things is hard. How do you prove that a GUI element actually popped up? You can fire events, but then it's not actually the mouse click that causes the event, it's some manual trigger which doesn't exercise the full code path. That's probably better than nothing, but it's tricky. [I've been grappling with this as I try to figure out how to test the apps I'm writing. However we approach this, I'd like the solution to be something VERY usable by people using the j-g bindings to write apps, as opposed to just the people hacking on the bindings themselves] FWIW, my vote would be JUnit since a) eclipse has extensive support for it b) it's widely used in the Java community. AfC Sydney --=20 Andrew Frederick Cowie OPERATIONAL DYNAMICS Operations Consultants and Infrastructure Engineers http://www.operationaldynamics.com/ Sydney: +61 2 9977 6866 New York: +1 646 472 5054 Toronto: +1 416 848 6072 London: +44 207 1019201 |
From: Jeff M. <ku...@gm...> - 2005-01-10 14:39:38
Attachments:
GtkTestCase.java
ComboBoxTest.java
|
On Sat, 08 Jan 2005 01:10:03 +1100, Andrew Cowie <an...@op...> wrote: > On Fri, 2005-07-01 at 08:50 -0500, Jeff Morgan wrote: > > And now on to the question. During our next development cycle we hope to > > introduce a testing framework for the java-gnome bindings. The question is > > "should this testing framework be based on JUnit or Mauve?". I am interested > > in your experience with both of these tools. > > [cut and paste from #java-gnome] > > Unit testing GUI things is hard. How do you prove that a GUI element > actually popped up? You can fire events, but then it's not actually the > mouse click that causes the event, it's some manual trigger which > doesn't exercise the full code path. Thomas Fitzsimmons wrote some code for the classpath project that provides a wrapper around the XTest library. I am sure this code could be used for java-gnome. I am also convinced that much of the bindings can be tested without even displaying a window. > [I've been grappling with this as I try to figure out how to test the > apps I'm writing. However we approach this, I'd like the solution to be > something VERY usable by people using the j-g bindings to write apps, as > opposed to just the people hacking on the bindings themselves] > > FWIW, my vote would be JUnit since a) eclipse has extensive support for > it b) it's widely used in the Java community. I just wrote a simple JUnit test for the ComboBox class. My goal was to see how easy it would be to write JUnit based tests for Java-GNOME. I have attached the source here. Please take a look and let me know what you think. > Andrew Frederick Cowie > > OPERATIONAL DYNAMICS > Operations Consultants and Infrastructure Engineers > http://www.operationaldynamics.com/ > > Sydney: +61 2 9977 6866 > New York: +1 646 472 5054 > Toronto: +1 416 848 6072 > London: +44 207 1019201 -- Jeffrey Morgan "The highest reward for a man's toil is not what he gets for it, but what he becomes by it" - Jon Ruskin |
From: Andrew C. <an...@op...> - 2005-01-10 21:58:44
|
On Mon, 2005-10-01 at 09:39 -0500, Jeff Morgan wrote: > that provides a wrapper around the XTest library. I mentioned XTest yesterday in #gnome-hackers, and people [metaphorically] vomited. They really were highly unenthusiastic. I have no idea why that was so but then I have no idea what XTest is. FYI. AfC Sydney |
From: Jeff M. <ku...@gm...> - 2005-01-10 22:11:35
|
On Tue, 11 Jan 2005 08:58:33 +1100, Andrew Cowie <an...@op...> wrote: > On Mon, 2005-10-01 at 09:39 -0500, Jeff Morgan wrote: > > that provides a wrapper around the XTest library. > > I mentioned XTest yesterday in #gnome-hackers, and people > [metaphorically] vomited. They really were highly unenthusiastic. I have > no idea why that was so but then I have no idea what XTest is. FYI. > The XTest docs say: "This extension is a minimal set of client and server extensions required to completely test the X11 server with no user intervention." Here are the links: http://64.233.167.104/search?q=cache:YPkpge9tNx0J:www.x.org/X11R6.8.1/doc/Xext/xtestlib.pdf+xtestlib.pdf&hl=en http://64.233.167.104/search?q=cache:aeIY611VT2UJ:www.x.org/X11R6.8.1/doc/Xext/xtest.pdf+xtest.pdf&hl=en |