Consider a bunch of scenarios grouped into one feature file that all setting up a valid user, however I do not want to generate such a user dynamically, for example:

  : Creating a new user and logging in
          Given the following user "<alias">
          When "<alias>" logs in

All scenarios require their own valid user, which based on alias is serialized from a .json file, how can I such a background step when I want to choose the alias of my user using a alias? how can each scenario get scope of their own user here, that is not reused throughout all scenarios? each scenario should have its own user created and such alias used is tied to each scenario.



Source link https://sqa.stackexchange.com/questions/32789/how-can-we-manage--background--when-require-hard-set--ali

LEAVE A REPLY

Please enter your comment!
Please enter your name here