Debug Mode

My friend and fellow teammate - Trung - has been spending time with me to help me understand how to debug failing tests and code.

He showed me how to put break points in Eclipse and then to run the test in debug mode. When it hits the breakpoint, the test can move line by line of the code - by hitting F6. F8, will run through the rest of it without break/stopping.

This has helped me zoom in closer to problems I was reporting. Such as a variable not being set before the page continues.

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.

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