How to get ATF test runs triggering cross-scope access requests?

[Christian Prob2]

I am trying to use ATF for a custom app.

It looks like when running the tests in the dev environment with Runtime Access Tracking set to "Tracking", the tests run nicely, but without triggering Cross-Scope Access requests:

When installing the app in the next higher environment (for example Dev Test) all tests fail due to missing Cross-Scope Access grants.

I can reproduce this in the Dev environment by setting Runtime Access Tracking set to "Enforcing".

The tests are created within the app, but need to access tables in global.

Preferably I'd like to understand how to get the ATF runs to trigger cross-scope access requests. 

Thanks, Christian

[mlee]

Hey Christian. It looks like part of the problem I was having was related to a setting in ATF that I had enabled.

"Enables tests with Custom UI steps to capture page data each time they are run. When true, Custom UI steps always refresh the page data during a test run. Disable this property to skip capturing page data during test runs. When false, tests run faster but Custom UI steps may not have the latest information due to stale page data. You can use 'Retrieve Components' to manually refresh page data before creating or editing a Custom UI step."

The limitation w/ the cross-scope violations still is an issue but I am able to work around it.