Add command to list all available step definitions

[bowsersenior]

There are a lot of step definitions in gauntlt, which fall into 2 categories:

1. Those defined by gauntlt
2. Those defined by aruba

This would look like:

$ gauntlt --steps

This feature will help users understand what they can do with gauntlt. It will also help us to pare down the number of steps to the number required and add an abstraction layer between gauntlt and aruba so that we can more easily drop our dependency on cucumber (either by using a replacement for aruba, or forking aruba to create a version of it that does not require cucumber).

[sarcilav]

Hey Guys, I'm kind of new to the project, and I'm really looking forward for this feature, please let me know if someone has some work on progress for this, or if I can help with this

[bowsersenior]

Definitely appreciate your help on this feature!

-Mani

Sent from my iPhone

On Mar 28, 2013, at 9:49 AM, Sebastian Arcila Valenzuela notifications@github.com wrote:

Hey Guys, I'm kind of new to the project, and I'm really looking forward for this feature, please let me know if someone has some work on progress for this, or if I can help with this

—
Reply to this email directly or view it on GitHub.

[sarcilav]

hey @bowsersenior I've an initial implementation that shows something like https://gist.github.com/sarcilav/5266167 if you see it is also listing the steps from aruba, please let me know what do you think and what should I add, remove ... change

[bowsersenior]

Fixed with #51. Thanks @sarcilav !

[bowsersenior]

Realized it would be beneficial to leverage the existing code in Gauntlt::Attack to call into the cucumber runtime. That way, all passed options will work with gauntlt --steps and future changes to the command line will be easier as a new `Gauntlt::Runtime`` class encapsulate cucumber's CLI and internals.

Also added a cuke feature for the gauntlt --steps command.

See: c4e4224

[sarcilav]

nice refactor :)
I still need to get more familiar with the code base of gauntlt

On Sun, Mar 31, 2013 at 10:38 PM, Mani Tadayon notifications@github.comwrote:

Realized it would be beneficial to leverage the existing code in
Gauntlt::Attack to call into the cucumber runtime. That way, all passed
options will work with gauntlt --steps and future changes to the command
line will be easier as a new Gauntlt::Runtime` class encapsulate
cucumber's CLI and internals.

Also added a cuke feature for the gauntlt --steps command.

See: c4e4224c4e4224

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/46#issuecomment-15704939
.

Sebastián Arcila Valenzuela