Test::BDD::Cucumber
Today on the way to work I almost finished off Test::BDD::Cucumber, but didn't quite manage it. So work having finished, I cracked out my MacBook Air and put the finishing touches in!
Choose your own adventure: if your reaction was:
WTF is Cucumber? - the tutorial
Where can I browse it? - MetaCPAN, GitHub
Well that's boring... - cat pictures to the rescue...
I blog about Perl.
Nice to see things ported from Ruby. But I wonder if I should use it instead of Test::More. The problem is, who usually writes better tests: the programmer himself, or the project manager, or the system analyst?
I'm not sure you need to choose between one or the other - Test::BDD::Cucumber is designed to work in conjunction with Test::More and the other Test::Builder modules...
I've started to see Cucumber primarily as a way of organizing tests. As a programmer still needs to write Step Definitions (and this is done using Test::More or any other Test::Builder module), the programmer is still implementing the tests - but a project manager or systems analyst can still make sure that the bases they want to see are covered - are covered.
I have not yet managed to "feel" how Cucumber would work for me but I was happy to see you made this.
Unfortunately the links to MetaCPAN did not work for me. They did not lead to the expected documents on MetaCPAN. Oh I see this might be a MetaCPAN issue as I can see the files on search.cpan.org
Gugod also wrote a port of Cucumber called Test::Cukes.
Perhaps you guys can bang your heads together on this?
/I3az/
PS. Hopefully this time my comment got through. First one got list :(