cstrom@whitefall:~/repos$ cd cucumber
cstrom@whitefall:~/repos/cucumber$ gem install gherkin cucumber therubyracer
cstrom@whitefall:~/repos/cucumber$ gem listWhile I'm at it, I pull new changes to cucumber. I still have the patch mostly lifted from Charles Lowell in place.
*** LOCAL GEMS ***
/home/cstrom/.rvm/rubies/ruby-1.8.7-p249/bin/ruby -I "/home/cstrom/repos/cuke.real/lib:lib" "/home/cstrom/repos/cucumber/bin/cucumber"
In order to calculate super fast fibonacci series
Scenario Outline: Series # features/fibonacci.feature:6
Then it should give me
| n | series |
| 1 |  |
| 2 | [1, 1] |
| 3 | [1, 1, 2] |
| 4 | [1, 1, 2, 3] |
Scenario: Single series with Before hook with a tag label # features/fibonacci.feature:41
Then it should give me [1, 1, 2] #
Scenario: Single series by calling a step from within a step # features/fibonacci.feature:45
Then it should give me [1, 1] via calling another step definition #
12 scenarios (12 passed)
21 steps (21 passed)
- reverting yesterday's cucumber patch
- reverting to therubyracer version 0.7.0
- even switching back to my "global" rvm gemset
Eventually, I do track this down. It turns out the patch that am using now is not quite the same as the one I used last night. Last night, I had used the following line directly from the patch in Charles Lowell's cucumber fork:
js_function.call(@world.scope, *js_args)Earlier today I manually patched the Cucumber source by searching and replacing
to_s. That left the above line in this state:
evalstatements are using in there. At this point, I am just happy to have it working. It would have been nicer if I realized it was working when I first made my "dumb" patch, but c'est la vie.
My complete patch, for what it's worth.