Currently we are running into a wall with re-usability. Either we don't use parameters,and there's no re-usability and alot of cloned code for one single functionality, or we use parameters and every test with "Call steps from another test" will have to set up all the parameters on test set run.

I propose a way to set parameter values on a test level. So when we use "Call steps from another test", all the parameters for that called test are possible to be set from within the current test, allowing for a lot more re-usability within tests. Not all should be set, like username and password, but maybe other fields like "Active" would have way to set its value to "true" or "false" for that particular test, which would be useful when I'm testing if something happens or not when a record is "Active".

I currently have four steps I must always run when I want to test creating a record. And I need to create this do these 4 steps in many different tests, when for example manipulating the record, or testing the feature overall.

So every time I need to make the record, it would be useful to "Call steps from another test", and fill in the correct values for the current test.

This allows for more configurability for tests on a test level, instead of doing all parameters when running the test, and having a hard time remembering what all the parameters are.