I’m happy you join Hiptest community.
When you use Classic Agile “Action/Result”, you often use a imperative style. As you are converting your tests using Gherkin syntax, you should refactor your tests using declarative style. You can find more arguments here: http://itsadeliverything.com/declarative-vs-imperative-gherkin-scenarios-for-cucumber.
Hiptest enables the capability to refactor your tests with the “promote” feature i.e.
by converting steps into an action word (https://hiptest.com/docs/refactor-scenarios/#promote).
The idea is to select steps that will give a line in Gherkin style and to create an action word.
When you apply the conversion, you can choose the new name of the step in declarative style and you can choose to apply the refactoring at the other places where the selected steps are used. This saves time .
Once conversion is done, selected steps are replaced by the call to the new action word everywhere you had choose.
You just need to choose the right keyword Given/When/Then (if you want, it is not mandatory for automation)
By using this method, you should be able to refactor your scenarios step by step.
By the way, I suggest you to configure step editor preferences of your project as “Automation Ready” (in project settings tab)
I hope this helps you.