Extending JUnit Rules

One of the common problems that I run into when trying to debug failed tests is visibility.  Specifically, which test failed, under what conditions.  One habit that makes this process simpler, for me, is logging test names at the start of each test executed.  The only problem with this practice is that it requires a lot of cut+pasting into each individual test... and that's a nuisance.

Web App Testing with Selenium and JUnit

I'm presenting the following slide deck tonight at the Seattle Java Users Group.  In my work for Dynacron Group, I test web applications using Selenium automation, written in Java, running using JUnit, through Sauce Labs cloud services.  This slide deck describes some of the challenges and tools I've used in this process.
 


The formatting is a little scrambled from conversion to a google doc.  Fair warning.

Welcome

This is David Drake's professional blog.  I intend to use this space to write about the development work I'm doing on Khaom Academy.  I'll also be writing here about general testing and development topics.

I'm currently a Seattle SDET for Dynacron Group.  I've been in the testing field for the last five years, but I'm also worked as a middle school math teacher, a merchant teller at a bank, a pizza cook and delivery driver, a technical writer, a tutor, a bagger, a janitor, a factory worker, and a day laborer.

Khaom Academy is a game I'm working on as a side project.  It's being built on the Google App Engine, using Java as the primary language.  This requires learning quite a few new-to-me technologies, so it has been slow to start.  These include:

• Spring MVC
• Jsp pages, with jstl
• JDO data storage, with Objectify

I'll talk more about the particular challenges I'm facing along the way, but in the meantime, those interested in starting a project on the App Engine using Java, Maven, and Spring should take a look at Mike's excellent blog which includes a fair amount of information on the subject.