Scenario Transform header being treated like an object

[mmalmeida]

This was found as I was creating a test case for #395.

A different behaviour is observed between 1.0.10 and 1.0.11 versions of cucumber in handling scenario transforms.

Consider the scenario:

Given the list for module XX:
    |question    |
    | Age         |
    | Height    |
When foo
Then bar

In 1.0.10, the stepdef with the signature public void the_list_below(String moduleName, List questions) (where ScenarioQuestion has a "question" attribute) creates a list of size 2 (age and height).

However, in 1.0.11 it creates a list of size 3 (question, Age and Height).

Why is it treating the header as a ScenarioQuestion object?

See the attached test case where that behaviour is observed (if you change the cucumber version in the pom.xml you'll see the junit test fails): https://github.com/mmalmeida/cucumber-playground/tree/master/cucumber-scenarioObjects

[aslakhellesoy]

I have only given this a quick analysis, and it looks like Cucumber is instantiating an instance per row because the list has a single column, and each single field in the column can be used to create an instance, using ScenarioQuestion(String).

I'll have to think more about this one...

[aslakhellesoy]

It's beacuse the String constructor makes Cucumber think it's a scalar: http://cukes.info/step-definitions.html

Lose the String constructor!

[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.