I'd like to see this not just for shared steps but for any step. That would make it easier to reuse test cases that might be identical for different tickets except for the data being passed, rather than needing to create a new one each time, adding a whole lot of repetition and unnecessary bulk to our test case repository.

This feature would be extremely useful especially for projects who are trying to migrate from Xray. In Xray they had a feature called modular tests where you could establish parameters and then when you implement the steps in an individual test case you could choose the necessary parameter specific to that test case instance. A good example of this would be considering something such as a navigation menu. If we were able to implement the navigation menu steps with menu options that are parameterized you can then have 1 shared step for the action of navigating around the app across hundreds of tests because then you could simply chose the correct menu option parameter in each individual test case instance

this would be extremely beneficial, please make this a reality soon!

So glad to see that it's already in planned category.

In a regulated industry like pharma, we must standardize the steps to speed up design and simplify review protocols by not IT personnel.

We standardize test steps per system to improve interpretation and easier align with functional specifications. To fully utilize the Qase platform, those steps must run with different entry data and expected values.

This approach will help QA people (not IT) to review protocols before execution quickly.

One use case would be to change a URL in a test case step based on the environment. So, for example, if you are running the test in a run in a staging environment you could have staging.example.com in the test case step, but in a run in a production environment the URL would be example.com

Hi everyone!

We saw a great interest in this feature recently, and we would like to know more about your use-cases.

Please, reach out to me directly by sending a message to ivolkov@qase.io to schedule an exploratory call.