Large Scenario Outline tables without having to explicitly mention all parameters in the step definitons
<p>In Python's <a href="https://behave.readthedocs.io/en/latest/index.html" rel="nofollow noreferrer">behave</a> library, I can write a feature file with a parametrised Scenario Outline like so (adapted from <a href="https://jenisys.github.io/behave.example/tutorials/tutorial04.html" rel="nofollow noreferrer">this tutorial</a>):</p>
<pre><code># feature file
Feature: Scenario Outline Example

  Scenario Outline: Use Blender with &lt;thing&gt;
    Given I put &quot;&lt;thing&gt;&quot; in a blender
    When I switch the blender on
    Then it should transform into &quot;&lt;other thing&gt;&quot;

    Examples: Amphibians
        | thing         | other thing |
        | Red Tree Frog | mush        |
        | apples        | apple juice |
</code></pre>
<p>The according step definitions would look like this:</p>
<pre><code># steps file
from behave   import given, when, then
from hamcrest import assert_that, equal_to
from blender  import Blender

@given('I put &quot;{thing}&quot; in a blender')
def step_given_put_thing_into_blender(context, thing):
    context.blender = Blender()
    context.blender.add(thing)

@when('I switch the blender on')
def step_when_switch_blender_on(context):
    context.blender.switch_on()

@then('it should transform into &quot;{other_thing}&quot;')
def step_then_should_transform_into(context, other_thing):
    assert_that(context.blender.result, equal_to(other_thing))
</code></pre>
<p>As one can see, the way to pass the parameters from the feature file into the step functions is</p>
<ul>
<li>by explicitly mentioning them in the feature file enclosed in angle brackets</li>
<li>then include the same words enclosed in curly brackets (why not angle brackets again?!) in the decorator of the step function</li>
<li>and finally insert these words as function arguments of the step function.</li>
</ul>
<p>However, given a larger example table with a lot of columns, this quickly gets annoying to write and read:</p>
<pre><code># feature file
Feature: Large Table Example

  Scenario Outline: Use Blender with a lot of things
    Given I put &quot;&lt;first_thing&gt;&quot;, &quot;&lt;second_thing&gt;&quot;, &quot;&lt;third_thing&gt;&quot;, &quot;&lt;fourth_thing&gt;&quot;, &quot;&lt;fifth_thing&gt;&quot;, &quot;&lt;sixth_thing&gt;&quot;, &quot;&lt;seventh_thing&gt;&quot; in a blender
    When I switch the blender on
    Then it should transform into &quot;&lt;other thing&gt;&quot;

    Examples: Things
        | first thing | second thing | third thing | fourth thing | fifth thing | sixth thing | seventh thing |
        | a     | b             | c  | d           | e            | f           | g           | h             |
        | i     | j             | k  | l           | m            | n           | o           | p             |

# steps file    
@given('I put &quot;{first_thing}&quot;, &quot;{second_thing}&quot;, &quot;{third_thing}&quot;, &quot;{fourth_thing}&quot;, &quot;{fifth_thing}&quot;, &quot;{sixth_thing}&quot;, &quot;{seventh_thing}&quot;,  in a blender')
def step_given_put_thing_into_blender(context, first_thing, second_thing, third_thing, fourth_thing, fifth_thing, sixth_thing, seventh_thing):
    context.blender = Blender()
    context.blender.add(thing)
...
</code></pre>
<p>I think the point is clear. Is there any possibility to transfer the examples from a large table into the step definition without having to mention all of them explicitly? Are they, for instance, saved somewhere in the context variable even without mentioning them in the text (could not find them there yet)?</p>