Enforce parameter names in steps questionAnswered
Is it possible on a project level to enforce parameter naming conventions in steps? For example take this step:
I perform a simple search on '(.*)'"
Is there a way to globally enforce a rule where, for example, the matching parameter is not allowed to contain a question mark or quote or the letter q or something else?
Yes, I know you can use regexes in the parameters but I want to enforce a global rule that will throw some kind of error if I use illegal characters in the parameter name.
Thank you in advance!
Please sign in to leave a comment.