ATF Click Component Step Passes but Does Not Click the UI Element
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
56m ago
I’m trying to determine whether this is an ATF issue or something specific to the On-Call Scheduling UI.
My ATF test reaches the Default Shift and then needs to click the Actions button. At that point, the Actions control never appears/becomes available, and the test cannot continue.
If I perform the same steps manually, the Actions button appears normally and I can continue without any issue. I've also impersonated multiple users to rule out an obvious user/role difference. The behavior remains:
Manual: Default Shift → Actions appears → works
ATF: Default Shift → Actions does not appear → test cannot continue
Has anyone encountered this difference between manual testing and ATF?
In particular, I’m interested in whether:
- ATF may be progressing too quickly before the control finishes rendering.
- The Actions control requires an asynchronous UI event that ATF isn't triggering.
- There is a better ATF step/assertion to wait for the Actions control before attempting the click.
- This is a known limitation with ATF and the On-Call Scheduling interface.
We are on Zurich release. Screenshots attached.
