From 07e7498030ed4e702a8381cbdfaa69f8f4386a2e Mon Sep 17 00:00:00 2001 From: Roman Lisagor Date: Wed, 17 Jun 2009 19:23:39 -0700 Subject: [PATCH] Removing multiline names as a feature because it's exorbitant --- cuke-comparison.txt | 6 +++++ .../self_test/features/multiline_name.feature | 27 ------------------- 2 files changed, 6 insertions(+), 27 deletions(-) create mode 100644 cuke-comparison.txt delete mode 100644 examples/self_test/features/multiline_name.feature diff --git a/cuke-comparison.txt b/cuke-comparison.txt new file mode 100644 index 0000000..0c65d62 --- /dev/null +++ b/cuke-comparison.txt @@ -0,0 +1,6 @@ +Differences from Cucumber: + +- Obviously, there are no magical assertion methods on objects, use nose.tools.* instead +- When calling steps from inside step definitions, you can pass a block of text which will get parsed the same way it does in a real .feature file +- You cannot have multi-line feature or scenario names + diff --git a/examples/self_test/features/multiline_name.feature b/examples/self_test/features/multiline_name.feature deleted file mode 100644 index 3bd458f..0000000 --- a/examples/self_test/features/multiline_name.feature +++ /dev/null @@ -1,27 +0,0 @@ -Feature: multiline - - Background: I'm a multiline name - which goes on and on and on for three lines - yawn - Given passing without a table - - Scenario: I'm a multiline name - which goes on and on and on for three lines - yawn - Given passing without a table - - Scenario Outline: I'm a multiline name - which goes on and on and on for three lines - yawn - Given without a table - Examples: - | state | - |passing| - - Scenario Outline: name - Given without a table - Examples: I'm a multiline name - which goes on and on and on for three lines - yawn - | state | - |passing| \ No newline at end of file