Tags: Java
am new to the
java.net blogging crew, and since this is my first posting here I thought to introduce myself.
My name is David Herron and I work in the Java SE Quality Engineering team. I have also been blogging at http://blogs.sun.com/robogeek if you want to see what I've been saying in the past, and I have a personal blog site at 7gen.com.
What I expect to bring to the
java.net blogs is exposure for the how Java is tested at Sun, and testing issues in general.
Why "Robogeek"? Read
The birth of Robot, Testing Java GUI applications & multiple platforms,
The bottom level of GUI automation tools etc. To summarize, I wrote the Solaris/Linux half of the original version of the java.awt.Robot class ... get it? Robot ==> RoboGeek? ...er... Never mind. It's probably too silly of a joke.
Anyway, for a long time I've been interested and working on in GUI test automation tools. I'll try to share some of that knowledge here.
In general what I find exciting about my job is the opportunity to contribute to the efficiency of the team that tests Java. To know that you all expect Java to be highly reliable, functional, perform well, and so forth, and the excitement is to be able to assist the team validates all that for y'all.
Source:
weblogs.java.net
Comments
Cool, I know it is on the border of breaking some kind of Sun code, buf could you present some of your approaches for you quality of the JSE.
I think it would be great for our projects, as well.
Posted by: blbrown on July 08, 2005 at 07:52 PM
Second that. I am interested in testing approach at Sun Micro. I am especially interested in knowing if Sun does "Test First Development" during the development cycle?
Posted by: tchangu on July 11, 2005 at 12:25 PM
