--no-multiline does not hide multiline strings

[thedjinn]

Consider the following example:

Feature: Hiding multiline strings and tables

    Scenario: Hiding tables
        Given a table:
            | foo  | bar  |
            | quux | ding |

    Scenario: Hiding multiline strings
        Given a muiltiline string:
            """
            hello world
            this is a long string
            """

From the command line usage you can see that the expected functionality of the --no-multiline option is as follows:

Don't print multiline strings and tables under steps.

However, running Cucumber with this option produces this output:

Feature: Hiding multiline strings and tables

  Scenario: Hiding tables # features/bug.feature:2
    Given a table:        # features/bug.feature:3

  Scenario: Hiding multiline strings # features/bug.feature:7
    Given a muiltiline string:       # features/bug.feature:8
      """
      hello world
      this is a long string
      """

The table is clearly hidden, but the multiline string is still visible.

[mattwynne]

I never cease to be amazed by the command-line switches people have added to Cucumber. Why would anyone want this option?

[thedjinn]

I use Cucumber mostly to spec out the behavior for command line applications. In that case the scenarios usually have the following structure:

Scenario: Foo
  Given a file named "foo" with:
    """
    some big file here, e.g. XML data
    """
  When I run `mycmd foo`
  Then the output should contain exactly:
    """
    some big output here
    """

If you have a lot of these scenarios then Cucumber's output will get very cluttered. By hiding the multiline strings you can get a clear overview of the steps involved without showing too much detail.

[mattwynne]

@tooky fancy taking a look at this one?

[tooky]

Ahh too late, @mattwynne - thanks @dkowis!

[dkowis]

@tooky I didn't pay attention before I noticed that @mattwynne poked you about it. I did it wrong the first time anyway :)

[os97673]

fixed by #418

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.