-
Notifications
You must be signed in to change notification settings - Fork 133
Issue79 #116
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Issue79 #116
Conversation
Any idea what happend on OSX? |
I have the same result. |
could you recheck? |
Still failing:
|
i think something is wrong with your envronment as everything is undefined including cucumber-tck that i haven't changed and all passes on CI... |
Quick notes:
...but in general a big 👍 for the feature file in the "specific" section :-) |
@konserw How can I check my env is ok? |
@MartinDelille not sure. At some point I've removed all ruby'ish :P You can try using RVM to change ruby version, or remove all gems |
@konserw There is indeed something wrong with my ruby/gem configuration, I'll try again when I'll find time to fix it. |
#include <vector> | ||
#else | ||
#include <array> | ||
#endif |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not in favour of duplicating the test that needs to be done to test both implementations. For now I'd stick to not using C++11. In the long run I'd rather do dynamic loading of step definitions so that they can be compiled separately from the core and convert it to C++11.
In general it is missing some of the special characters in regexes. The feature description is talking about testing. Cucumber is about communication!
It might also be a good idea to use scenario outlines instead of copy/paste/change of the same feature. Your scenarios transformed in a Scenario Outline:
Second iteration:
Final result:
Edit: the Examples block is wrong and doesn't take Gherkin escaping into consideration |
I had this feeling that copy-paste was wrong way to do it - thank you ;) |
Double quote scenario appears as undefined - do you know how to fix that? Probably I got my step definition wrong? |
Please check now if it is all ok |
Thanks for your contribution but I don't think your current implementation is correct, and e2e tests pass because the feature file is incorrect (perhaps you fixed the scenario based on the result of your implementation instead of the other way around?). Try to add this feature to the Calc example:
Your snippet is
that doesn't compile. Spent a lot of time today trying to understand the bizarre escaping in Gherkin, and came up with paoloambrosio/cucumber-cpp@07d7e6b (konserw-issue79 branch). I've also refactored the code splitting the escaping of the two, regex and c-string, as well as added unit tests. With that the generated snippet for the aforementioned feature is
that compiles and matches. Feel free to squash your commits and pull mine into this PR. |
BTW, I've created cucumber/cucumber-ruby#1006 for the bizarre escaping in Cucumber-Ruby. |
Introduced unit tests Fixed feature file, with bizarre escaping behaviour
Done :) |
Built this on my repo before merging as the build wasn't working in this branch. It worked in the end :) Finally merged! |
Fix for issue #79 - Suggested step definition when step sentence contains double quote