Comments for rapaul.com

Comment on Gherkin Highlighting for VIM by Jorge O.

Jorge O. — Mon, 26 Mar 2012 15:33:43 +0000

The original post instructions didn’t work for me, I followed Brent J. instructions and now is working OK.
thanks Brent.

Comment on Gherkin Highlighting for VIM by Joe magni

Joe magni — Tue, 07 Feb 2012 02:12:57 +0000

Thanks everyone! Jim Hopp – you made my day! I am just getting started in the Gherkin, Sinatra, Capybara, Cucumber, Ruby world. And having vim being able to display syntax in colors is helpful! Thanks again!

Comment on Cucumber, Maven & TeamCity by What I’ve learned about Acceptance Testing « alexcuesta

What I’ve learned about Acceptance Testing « alexcuesta — Thu, 02 Feb 2012 21:30:33 +0000

[...] every commit but not the less important ones. Those ones were run every 3 hours or nightly. This post by Richard Paul explains it very [...]

Comment on From zero to headless browser tests in Jenkins by Richard Paul

Richard Paul — Wed, 01 Feb 2012 04:34:20 +0000

Hi Paresh,

I’ve not tried installing Jenkins on Windows, but I’m fairly sure Xvnc won’t work as it is related to http://en.wikipedia.org/wiki/Xorg which is generally used on Linux type systems.

The Jenkin’s mailing list might be your best port of call.

Comment on From zero to headless browser tests in Jenkins by Paresh Mahajan

Paresh Mahajan — Tue, 31 Jan 2012 09:48:33 +0000

hi,
In my case, Jenkins server is installed on windows server 2003 where I dont have vnc server installed.
So to view the headless execution of browser tests (in my case selenium), I have only one option to remote desktop that machine.

Now, though I connect via remote desktop to the server, I cant see the scripts running with opened browser. I have installed Xvnc plugin and checked the same in job configuration.

Can you help me here: how to see the opened browser to debug some failing script on jenkins server(which passes locally)?

Comment on Gherkin Highlighting for VIM by Steve Love

Steve Love — Tue, 20 Dec 2011 17:47:38 +0000

It looks like the vimrc filetype and syntax commands listed here aren’t necessary. The cucumber.vim plugin on its own works perfectly.

Comment on Gherkin Highlighting for VIM by Jim Hopp

Jim Hopp — Tue, 06 Dec 2011 19:45:44 +0000

Instructions above didn’t work for me (MaxOSX 10.6.6, vim 7.2.108).

I was able to get it to work by doing this:
1. Move ~/.vim/cucumber.vim to ~/.vim/syntax/gherkin.vim
2. Remove the “au!” line in ~/.vimrc

Comment on Constructor injection, and how it simplifies unit test setup by Ricardo

Ricardo — Sat, 24 Sep 2011 12:02:01 +0000

Hi Richard

Don’t get me wrong, I agree there are a lot of benefits to constructor injection.

I will note that even just 3-4 constructor arguments can look ugly, especially if you need to annotate them with named qualifications, etc.

I think Fowler probably said it better than I could:

http://martinfowler.com/articles/injection.html#ConstructorVersusSetterInjection

Of course, the most important benefit of setter injection is that its the most widely used and therefore easiest to grok convention. Maybe something of a Betamax vs VHS thing.

Comment on Constructor injection, and how it simplifies unit test setup by Richard Paul

Richard Paul — Sat, 24 Sep 2011 11:29:04 +0000

Hi Ricardo,

You are right, my post was a little one-sided :)

The fact that setters include the name of the property does make them easy to read. But I would say with tooling support in IDEs this isn’t a problem when writing the code. And when reading the code the variable name for the arguments makes them self explanatory. e.g. new ItemChecker(itemFetcher, notifier)

I also think that an object that has more than 3 or 4 collaborators is a smell, being confused over the ordering of 8 constructor arguments should be guiding us to split the class into smaller more cohesive classes.

I guess what I’m trying to say is, there are very few situations where I feel a setter is preferable :)

Comment on Cucumber World with Groovy by Richard Paul

Richard Paul — Sat, 24 Sep 2011 11:18:15 +0000

Hi Phil,

I would recommend using Geb, a groovy library for driving browsers. It sits on top of Selenium.

I talked about it at SkillsMatter a while back, check out:
http://www.rapaul.com/2011/01/26/agile-acceptance-testing-with-geb/
http://skillsmatter.com/podcast/agile-testing/acceptance-testing-with-geb