Several Pre-defined steps not working When I click on element having text "text" command not working

[shanisko]

Steps in feature that are not working as pre-defined steps: (These are the one's I have located so far)

Does not automatically provide the step definitions as the other commands do:
10 scenarios (1 undefined, 9 passed)
72 steps (5 skipped, 1 undefined, 66 passed)
0m19.841s

You can implement step definitions for undefined steps with these snippets:

When I click on element with the text "/html/body/div[2]/div/div[4]/div/div[2]"
When(/^I click on element with the text "([^"]*)"$/) do |arg1|
pending # Write code here that turns the phrase above into concrete actions

When I choose radio button "//section[@id='account-selection']/div[2]/input[@id='auth-method_']"
When(/^I choose radio button "([^"]*)"$/) do |arg1|
pending # Write code here that turns the phrase above into concrete actions
end

When I check "toc_nametoc"
When(/^I check "([^"]*)"$/) do |arg1|
pending # Write code here that turns the phrase above into concrete actions
end

[Shashikant86]

@shanisko Thanks a lot for reporting the issue. I managed to reproduce and hopefully fixed the issue.
It seems like Cucumber has changed regular expression format recently. I have pushed new version of the gem bddfire 2.0.8. Please update bddfire gem by reinstalling it or

                              $ gem update bddfire 

Hope this should resolve the issue. Let me know if not

[shanisko]

Awesome! I will let you know on Monday if it worked. Sarah

…

Sent from my iPhone

On Feb 4, 2017, at 12:37 AM, Shashikant ***@***.***> wrote: @shanisko Thanks a lot for reporting the issue. I managed to reproduce and hopefully fixed the issue. It seems like Cucumber has changed regular expression format recently. I have pushed new version of the gem bddfire 2.0.8. Please update bddfire gem by reinstalling it or $ gem update bddfire Hope this should resolve the issue. Let me know if not — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[shanisko]

Uninstalled 2.0.7 and installed 2.0.8 and receiving this: (When I attempt to run using bundle exec cucumber it asks for 2.0.7. When I run bundle install after installing 2.0.8 it seems to revert to 2.0.7 and I still get the same issues above.

Select gem to uninstall:

1. bddfire-2.0.7
2. bddfire-2.0.8
3. All versions

1
Successfully uninstalled bddfire-2.0.7
greelys-iMac:BDD-Cucumber sarah.hanisko$ bundle exec cucumber
Could not find bddfire-2.0.7 in any of the sources
Run bundle install to install missing gems.
greelys-iMac:BDD-Cucumber sarah.hanisko$ bundle exec cucumber
Could not find bddfire-2.0.7 in any of the sources
Run bundle install to install missing gems.
greelys-iMac:BDD-Cucumber sarah.hanisko$ gem uninstall bddfire
Remove executables:
bddfire

in addition to the gem? [Yn] y
Removing bddfire
Successfully uninstalled bddfire-2.0.8
greelys-iMac:BDD-Cucumber sarah.hanisko$ gem install bddfire
Fetching: bddfire-2.0.8.gem (100%)
======== Thanks for installing BDDfire. You can now perform Web, API, Mobile, Accessibility, Load Testing with single framework !!====================
Successfully installed bddfire-2.0.8
Parsing documentation for bddfire-2.0.8
Installing ri documentation for bddfire-2.0.8
Done installing documentation for bddfire after 0 seconds
1 gem installed
greelys-iMac:BDD-Cucumber sarah.hanisko$ cucumber
Could not find bddfire-2.0.7 in any of the sources
Run bundle install to install missing gems.
greelys-iMac:BDD-Cucumber sarah.hanisko$

[Shashikant86]

@shanisko It looks like you need to delete Gemfile.lock as bddfire version 2.0.7 is locked in that file.

Try deleting Gemfile.lock and then do bundle install this should download new version of bddfire in the bundler. Now you can execute bundle exec cucumber

I think that will fix it :) Let me know i f not