Comments on: How to list all cucumber step definitions http://www.natontesting.com/2009/12/18/how-to-list-all-cucumber-step-definitions/ nathaniel ritmeyer's thoughts on automated software testing Thu, 19 Jan 2012 15:37:28 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nat http://www.natontesting.com/2009/12/18/how-to-list-all-cucumber-step-definitions/comment-page-1/#comment-312 Nat Mon, 22 Mar 2010 18:59:52 +0000 http://www.natontesting.com/?p=611#comment-312 What... with "-f stepdefs"? With my script? (Yeah, that won't work) With cucumber? What… with “-f stepdefs”? With my script? (Yeah, that won’t work) With cucumber?

]]> By: Jorge http://www.natontesting.com/2009/12/18/how-to-list-all-cucumber-step-definitions/comment-page-1/#comment-311 Jorge Mon, 22 Mar 2010 17:58:01 +0000 http://www.natontesting.com/?p=611#comment-311 I'm using pickle and I have been unable to use --dry-run with it I’m using pickle and I have been unable to use –dry-run with it

]]> By: Nat http://www.natontesting.com/2009/12/18/how-to-list-all-cucumber-step-definitions/comment-page-1/#comment-280 Nat Sun, 31 Jan 2010 21:25:02 +0000 http://www.natontesting.com/?p=611#comment-280 Hi Aslak, there's an even better version here: http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/ ...which mentions using the -f stepdefs formatter. What I wanted was to create a 'dictionary' of step definitions to give to people who write tests. The usage formatter does that but since it also lists where the steps are used in feature files it adds noise to the output I wanted. What I ended up using is: cucumber -d -f stepdefs ...because it lists only available step definitions, not where they are used. Hi Aslak, there’s an even better version here:

http://www.natontesting.com/2010/01/11/updated-script-to-list-all-cucumber-step-definitions/

…which mentions using the -f stepdefs formatter. What I wanted was to create a ‘dictionary’ of step definitions to give to people who write tests. The usage formatter does that but since it also lists where the steps are used in feature files it adds noise to the output I wanted.

What I ended up using is:
cucumber -d -f stepdefs

…because it lists only available step definitions, not where they are used.

]]> By: Aslak Hellesøy http://www.natontesting.com/2009/12/18/how-to-list-all-cucumber-step-definitions/comment-page-1/#comment-279 Aslak Hellesøy Sun, 31 Jan 2010 19:24:24 +0000 http://www.natontesting.com/?p=611#comment-279 Better: cucumber --dry-run --format usage features Better:

cucumber –dry-run –format usage features

]]>