GraphQL request for repository right after adding external service and waiting for repo to be mirrored returns null (even though UI shows repo)
Created by: felixfbecker
The browser extension e2e tests for Bitbucket always fail for on the first test (even if changing order of the test), but work on the second test or after reloading the page. It also works if adding a significant artificial delay.
The test
- Creates a Bitbucket external service pointing to a localhost Bitbucket Server instance, configured to clone one repo. If it already existed it deletes it first.
- Goes to the repositories page and waits for that repo to show up
- Note this is the critical step - given it shows up in the UI (after waiting a short while) I would expect it to not return
nullin the API.
- Note this is the critical step - given it shows up in the UI (after waiting a short while) I would expect it to not return
- Goes to Bitbucket to get code intelligence through the browser extension
- Fails because the browser extension gets a
nullresponse and does not add buttons / code intelligence
Here's a recording: https://www.loom.com/share/3c49d17539e84f63902844b1ab35308a