Pass a parameter to stage

[thejuliakors]

It would be cool to have an opportunity to pass a parameter to the stage. It's possible to do this via parametrize mark, however, there can be cases when we want to pass the parameter we received and saved during previous stages.

I.e. we create two entities (in different ways / with different test data and in different stages) and then we want to delete them and pass the ID of each entity to the delete-stage. In order to do that we should write two very similar stages instead of one and passing first_entity_id/second_entity_id to there.

- id: create_first_entity
   ...
   save:
        json:
          first_entity_id: id

- id: create_second_entity
   ...
   save:
        json:
          second_entity_id: id

- id: delete_first_entity
    name: delete the first smth
    request:
      url: "{tavern.env_vars.API_URL}/v1/admin/smth/{first_entity_id}"
      method: DELETE
      headers: *headers
    response:
      status_code: 204

  - id: delete_second_entity
    name: delete the second smth
    request:
      url: "{tavern.env_vars.API_URL}/v1/admin/smth/{second_entity_id}"
      method: DELETE
      headers: *headers
    response:
      status_code: 204

Maybe, there is some way to do that?
If not, it would be a nice enhancement.

[gc-ss]

Could you make this work with parameterized fixtures?

[thejuliakors]

Could you make this work with parameterized fixtures?

As far as I know, I can't pass parameters, which I receive in the middle of the test, to the fixture. Of course, I can pass the whole flow to the fixture, write the functions with the parameters I need, and reuse them from this fixture. Or copy-paste as many stages as is needed (like in the example above delete_first_entity/delete_second_entity). For sure there are ways to achieve what I need, however, I'm looking for a nicer one :)

[michaelboulton]

If you're implying you want to be able to dynamically create stages from parametrised input, that isn't really likely to ever happen because there are a few places where Tavern depends on knowing what is on the source line of the stage.

Personal opinion, but it also makes it a bit confusing where each stage could be expanded to multiple stages depending on user input, so what you're seeing in the file isn't showing the full picture of what stages would actually be run

[michaelboulton]

This might be a case where #1011 could be used, added a short test to show how it could be done: https://github.com/taverntesting/tavern/pull/1011/files#diff-388c6ed9b34b7d6fd570403b8211a56bc7ce6b3346c31c610843026bd4313bb6R240-R259