HTMLUnit

Victor and I set up forking logic to support HTMLUnit and FF. That way we'll have the ability to call a headless client test or a Firefox browser in the acceptance test run.

setup: properties files.

We're now using a properties file to define which db we are running acceptance tests against. Since we have several QA environments, we need to be able to call these different login scripts to each db.

This is pretty cool. Victor showed me how to set up the properties file to support our different environments

I work with some really cool Dev's... so on my Pilot team, they took the time out to help me with my Eclipse env issues from this weekend.

The DB errors were only specific to one specific test. My other tests were good (db connection wise) so i was on the right track. that feels good.

My acceptance tests weren't running because I was not extending them correctly! Victor, the dev I'm working with, showed me that I need to set up the Acceptance Tests and extend them correctly to the right class. This resolved the JUit issue - now I see "run as JUnit" avail for my tests.

Eclipse... grr....

This was a hair pulling weekend.

I got pretty pissed off with Eclipse. it somewhat balanced with my initial Java application success in the last post. Now I'm frustrated as I can't run any of the damn acceptance tests!

It's an eclipse environment problem. Eclipse is complaining it can't communicate with the database. I'm also not getting the JUnit option when running the classes i've made... grr.

My First Working App in JAVA!

OK - This weekend I got Eclipse set up. I've been working the past couple weeks in picking up Java. I found I couldn't really find resources to teach Groovy without first learning Java. Most Groovy resources are written to Java dev's. So I started with Java. I've been learning the JAVA basics so I can now pick up Groovy.

Backwards, I know, but I don't know how else to attempt this!

I've successfully written a few small applications in Java. I wrote a small application that uses selenium libraries to go to Google and pass a search term, then pull the results and report them back in Eclipse/IDE.

That was cool. My first working app in Java.

Leaving the Selenium IDE Crutches

When we started the pilot, I would write tests in Selenium IDE (just recording actions) then convert those scripts to Groovy and pass them to the developers. These developers would then write out the actual tests.

The Architect has made a request today: He wants QA to start writing the acceptance tests.

I'm a bit nervous - this is entirely new to me. New ground... but, damnit i'm going to do it. I'm going to get this done. I'm taking the work laptop home tonight and I have these goals:
a) get eclipse installed
b) download our acceptance tests repository locally
c) get maven and maven plugin for eclipse installed
d) install groovy
e) load in the acceptance tests correctly

So I've been on the Pilot Program to achieve a foothold into the continuous integration/deployment realm.

We have an architect leading our work. His name is Josh. Josh has worked with Thoughtworks and has some interesting ideas.

Our main goal is to get a framework of acceptance tests that extend out as we create new features in this team.

As we get a new project, we will create the tickets with a format of: Given, When, Then. All projects are consumer driven.

These tickets with the Given, When, Then breakdown are then translated into acceptance tests.

The acceptance test framework is this built with each new feature or enhancement.

An example is this:
Feature ABC:
As a user, I want to see XXXXXXXX when I enter my XXXXXXXX.

Given a logged in user

When they enter XXXXXXXXX

Then they will see XXXXXXXXX.

This is how the ticket would be formatted.

From that, the dev's are writing acceptance tests in Groovy - using Spock - to keep the same framework.

It's been decided that we'll be using Groovy and Spock for the Acceptance Tests.

First Post

Well I was informed I'll be on a new and exciting project.

Continuous Integration and Continuous Deployment is a big concept these days. A lot of people talk about it, and have various ways of implementing it.

Here at eHarmony - we'll be tackling this ourselves.

My background is QA. I'm a QA Eng. I haven't used an IDE and haven't developed in Java before.

I'm a bit timid of what to expect. This is a journal of my experience along the way of this process.