How can I use my "Given that a user is generated" step in multiple Features? (The other steps in those features will use the response)

[GyorgyOlah]

Is there a way to make a CommonSteps Class which will be the parent of my other StepDefinition classes?
So if there is a step which I use in multiple features I don't need to duplicate code.
( I don't want it to run before every scenario. It's just a step what is frequently used and I need the response of the API call in the step)

[Code-Grump]

I'm not sure I fully understand the question.

The default behaviour is that steps are globally available to features, independently of the class which they are attached to. You could define each step on a separate class if you wanted to!

[GyorgyOlah]

Okay I try to clarify:
So there is a step which calls a an API endpoint, and I need data from that response in the further steps.
StepDefinition looks like this :

    [When(@"I  login with an ""(.*)"" user")]
    public async Task ISumbitLoginRequest(String userType)
    {
        var request = BuildLoginAPIReqiest(_config,userType));
        _apiLoginResponse = await _e2EHttpClient.SendAsync(request);
    }

And I need _apiLoginResponse in the further steps. (More precisely the token parameter from the response)

How can I avoid having to write this step in every stepDefinition class?
(I have like UserLimitStepDefinitions,PaymentStepDefinitions,UserAccountManagementStepDefinitions and so on.)

[zdmta]

@GyorgyOlah here you can use hooks, like Before scenario or BeforeTestRun and store your api response in context or use container to register it and whenever you need it you can get that from context or by DI, documentation: https://docs.reqnroll.net/latest/automation/hooks.html

[GyorgyOlah]

Oh, and with hooks I can change the userType in the feature file for every scenario? Or I need to separate features based on user types? And what happens if the userType depends on a previous step response?

[zdmta]

you can use beforescenario hook and do any changes, or use tags to flag user type and load what you need base on that. https://docs.reqnroll.net/latest/automation/scoped-bindings.html or here some example in code: https://docs.reqnroll.net/latest/automation/scoped-bindings.html#id8

[zdmta]

if it depends, store it in scenario context and load in next step

[GyorgyOlah]

Context Injection for the wins. Thank you.