Saving values/return values from steps for later use/steps

[MichaelBarulin]

Hello,
I'm looking for an idiomatic solution for passing values to later steps without relying on the return value of fixtures.
Consider the following case:

`Scenario:Change a value on a website

Given I have a website showing value X

When I press a button showing +5

And I do some other action

Then value X should change by +5`

I'd like to avoid having a step specifically reading a value, and even if I did, it shouldn't cache the value since it could be used multiple times in a step, but at the same time calling it after an action it would return the new, modified value. In a regular test, one would simply save the value to a variable and compare it afterwards - what would be the best approach here for saving a value for future comparison?

[jsa34]

This seems like a candidate for scenario outline, so that you can change the value to be different (e.g. +5, -5, 0) and create a new test automatically for each value where each row is substituting the value of changes so each step can reference the heading of the examples table to get the value for each test. I would suggest looking at scenario outlines in the documentation. Let me know if this isn't what you meant!

[MichaelBarulin]

Thanks for the reply.
Unfortunately, that is not quite what I meant - I'm already using scenario outlines. What I'm trying to achieve is that a step first reads a value, which I don't know beforehand, then have another step increase this value by some action.
To correctly verify the step, I need knowledge of the value before the operation (e.g. it was 7). When another step presses a button (e.g. +5), the assertion should be able to verify the new value (e.g. 12). What is a good way to store the first value (in this example, 7) so an assertion can later access it? Variables go out of scope, and calling a fixture to read the value on the website would return the already changed value.