What’s Wrong with Geb

I was looking for the best browser level testing system for uSDLC. For a developer Geb is very seductive. It has good code reuse, excellent documentation and acceptable structure. So, I activated all of The Book of Geb in uSDLC. My most recent step was to start using get for document/test driven work on the uSDLC tasking module. And here I stated to see the limitation. When your Geb code fails the error messages are very obscure. I tried to retrieve the value of an attribute that did not exist. The result is a null pointer exception deep in Geb that took a lot of time to trace back. This happened time and again making test driven exhaustingly slow – limiting productivity and quashing creativity.

uSDLC does Geb well, but I will be trying pure Selenium next to see if it provides a better environment.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s