title: Python Behave - how to pass value from a scenario to use in a fixture on a feature level?
body: <p>I have the following test scenario:</p>
  
  <ol>
  <li>Check if project with a specific name was created</li>
  <li>Edit this project</li>
  <li>Verify that it was edited</li>
  <li>remove this project as part of a teardown procedure</li>
  </ol>
  
  <p>Here is an example code to achieve that:
  Scenario:</p>
  
  <pre><code>  @fixture.remove_edited_project
    @web
    Scenario: Edit a project data
      Given Project was created with the following parameters
        | project_name             |
        | my_project_to_edit       |
      When I edit the "my_project_to_edit" project
      Then Project is edited
  </code></pre>
  
  <p>Step to save the data in some variable to be used in a teardown function(fixture):</p>
  
  <pre><code>@step('I edit the "{project_name}" project')
  def step_impl(context, project_name):
      # steps related to editing the project
  
      # storing value in context variable to be used in fixture
      context.edited_project_name = project_name
  </code></pre>
  
  <p>and an example fixture function to remove a project after scenario:</p>
  
  <pre><code>@fixture
  def remove_edited_project(context):
      yield
      logging.info(f'Removing project: "{context.edited_project_name}"')
  
      # Part deleting a project with name stored in context.edited_project_name
  </code></pre>
  
  <p>In such a configuration everything works fine and project is deleted by a fixture in any case(test failed or passed). Which is alright.</p>
  
  <p>But, when I want to execute such a feature on a Feature level, means placing <code>@fixture.remove_edited_project</code> decorator before Feature Keyword:</p>
  
  <pre><code>@fixture.remove_edited_project
  Feature: My project Edit feature
  </code></pre>
  
  <p>, then this is not working. 
  I know the reason already - the context.edited_project_name variable is cleaned after every scenario and it's no longer available for this fixture function later.</p>
  
  <p>Is there any good way in passing a parameter somehow to a fixture on a feature level? Somehow globally?
  I was trying to use global variables as an option, but this started to be a bit dirty and problematic in this framework.</p>
  
  <p>Ideally it would be to have something like <code>@fixture.edited_project_name('my_project_to_edit')</code></p>