QA E2E tests on GDK - the setup of the tests can fail on Access Token creation
I have noticed that when running QA tests against GDK (master or branches) they can often fail when creating the token.
The issue seems to be that the name is not entered. Thus the token is not created and the test being ran fails as it cannot find the created_access_token
element (that does not exist due to no name)
I did a bit of digging and found when I added a pry breakpoint to step through, that it was successful, I'm guessing that there was a race condition that for some reason was preventing the name field from being immediately filled in. Adding a 2 second sleep here caused this to always be successful. I have a branch with a proper retry that I shall push up as an MR.