We currenty have failing end-to-end tests for the admin-part of our Confluence app, because of this new spotlight popup “Automation is now available on Free and Standard plans”?
We are used to these popups, but what’s new with
this popup is that it is a modal dialog. So, it’s completely blocking all other interaction with the page. So, we
have to deal with it and cannot ignore it. That’s currently blocks our end-to-end tests.
My ask: I understand the use of spotlight popups, but can Atlassian please refrain from using
modal popups which cannot be ignored?
@dmorrow, tagging you in the hope to speed things up.
8 Likes
Or could we not have popups on non-production systems. Or atleast be able to disable them on non-production systems. Popups which are essentially marketing end up costing us money in terms of failed e2e tests and man hours to figure out the reason behind it
8 Likes
Thank you for sharing. I’ve forwarded this on to the owning internal team.
3 Likes
This could be easily avoided if state of popup (shown / not shown) would be saved server side, not client side.
This is workaround I received in ECOHELP-52595 :
Update the browser local storage to set a value to indicate it’s already been seen.
localStorage.setItem("localStorage/atlassian.<AAID>.frontend.automation.onboarding", "\"true\"");
where is the AAID of the test user you are using:
https://<sitename>.atlassian.net/wiki/people/<AAID>
Please note that if nothing changes, this situation will occur again in the future with every new popup, as it was happening in the past.
Other possible solution is: for every new popup you would publish local storage values, which we can then add to our setup. Not as elegant as saving things server side, and adds more work, but would work for me.
3 Likes
I join this petition. As a QA engineer, the sudden appearance of popups is not only increasing the economic cost of pipeline executions, but also reducing the confidence of developers in functional tests.
Therefore, it would be awesome to have a mechanism to disable them in our testing instances.
1 Like
@TylerBrown, do you have an update for us? Did the internal team respond in any way?
