However, we lose tha ability to just fire the request out of Postman itself, without finding a good way to actually specify values for the variables.
The current way is to add a pre-request script, which fills the variables with appropriate values prior sending the request.
Is there another, better way? Especially to ensure completeness (that is, ensuring that every possible variable actually gets a meaningful value?)...
Regardless of the above question, this approach should be documented in the repo´s readme.
When authoring parameterizable postman-collections, we end up in collections containing requests that for themselfs might not be executable anymore.
E.g.: the following request is not executable without specifying values for the given variables (like via an environment?!):
We need to ensure that Postman knows about the two variables
firstName
andsurname
.When automating these requests, this is quite straight forward, by leveraging one of the
IVariableContext
-implementations:and later:
However, we lose tha ability to just fire the request out of Postman itself, without finding a good way to actually specify values for the variables.
The current way is to add a pre-request script, which fills the variables with appropriate values prior sending the request. Is there another, better way? Especially to ensure completeness (that is, ensuring that every possible variable actually gets a meaningful value?)...
Regardless of the above question, this approach should be documented in the repo´s readme.