Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal idea: Incorporate capability to call turnip features from within rspec #159

Closed
lukaso opened this issue Jul 3, 2015 · 1 comment

Comments

@lukaso
Copy link
Contributor

lukaso commented Jul 3, 2015

We've developed a gem https://github.com/simplybusiness/rutabaga which allows turnip features to be called from within an rspec declare block.

This allows users to avoid the complexities of having lots of @ flags on their features, and makes it easy to use features to test controllers in rails (for example). This functionality is similar to how I believe CucumberJVM works.

The reason for suggesting incorporating it, is that it has had to be built essentially as a monkeypatch on top of turnip, whereas I believe incorporating it in, would clean the code up. But equally, it needs to be useful as a core capability.

I suppose the other approach would be to add hooks to jnicklas/turnip to make the feature less of a monkeypatch.

@gongo
Copy link
Collaborator

gongo commented Jul 3, 2015

Hi @lukaso . Thanks for proposal.
But, I think turnip is not necessary to incorporate its feature.

Turnip's work is to provide a mechanism "linking from the scenario to the test case" only.
If add a reverse mechanism, how to use turnip becomes complex.
And, turnip's source code becomes complex instead of rutabaga.

(Therefore, it is very good that another gem (rutabaga) has a reverse mechanism.)

@gongo gongo closed this as completed Jul 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants