@gray-kilobyte-89541 when you guys were porting your selenium tests (its in your video: "How We Introduced Automated Web App Testing in A Large Organization | ReactNext 2021" at 24:13 -- did it ever evolve into something that required making an API call to create the user (say its a checkout flow that has steps 1,2,3), and that API call, creates a user that the script uses for automation testing, the user is set to step 2 of the flow? (reason: to speed up automation) --if so -- in your organization, did everyone maintain it? -- ours is a bit different.. since ours is subscription based -- sorry last question for me for today, really thank you for all the help -- also no need to answer, if not comfy enough to answer, thats all thx