How to test/run feature using cucumber via URL?
dholcombe
people can share the feature files. However it looks like I haven't
set everything up correctly as cucumber is having trouble finding the
related step files. Is there a particular piece of documentation I
should be referring to when attempting to set this up? When running
everything from local files these tests are working OK, so I've
obviously missed something.
Here's what I'm seeing when attempting to test a feature via URL
C:\>cucumber http://server/testing/login.feature
Feature: Cucumber Watir Demo
Scenario: Login to the development store. # http:\
\server\testing\login.feature:3
Given I am on the Home page on server/vroot # http:\\server
\testing\login.feature:4
Then I should see the "Login" link # http:\
\server\testing\login.feature:6
When I click the "Login" link # http:\
\server\testing\login.feature:7
--------------clipped here to keep it short----------
1 scenario (1 undefined)
9 steps (9 undefined)
0m0.016s
You can implement step definitions for undefined steps with these
snippets:
Given /^I am on the Home page on server\/vroot$/ do
pending # express the regexp above with the code you wish you had
end
Then /^I should see the "([^\"]*)" link$/ do |arg1|
pending # express the regexp above with the code you wish you had
end
When /^I click the "([^\"]*)" link$/ do |arg1|
pending # express the regexp above with the code you wish you had
end
Then /^I should see the "([^\"]*)" text field$/ do |arg1|
pending # express the regexp above with the code you wish you had
end
If you want snippets in a different programming language, just make
sure a file
with the appropriate file extension exists where cucumber looks for
step definitions.
Matt Wynne
On 13 Apr 2010, at 01:31, dholcombe wrote:
> I'm attempting to run my cucumber tests from a URL so that multiple
> people can share the feature files. However it looks like I haven't
> set everything up correctly as cucumber is having trouble finding the
> related step files. Is there a particular piece of documentation I
> should be referring to when attempting to set this up? When running
> everything from local files these tests are working OK, so I've
> obviously missed something.
If you use -v use can see the files that Cucumber is loading, which
might help.
I'd expect it will still look in './features/step_definitions' for the
step def code, even if you've pulled the feature itself from HTTP.
Were you expecting the step defs to be loaded via HTTP too?
> --
> You received this message because you are subscribed to the Google
> Groups "Cukes" group.
> To post to this group, send email to cu...@googlegroups.com.
> To unsubscribe from this group, send email to cukes+un...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/cukes?hl=en
> .
>
cheers,
Matt