You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests of web-applications that create data grids & histograms sometimes require asynchronous JavaScript calls to the presentation vendor's API, for instance, with Tableau.
waitForJavascriptCallback() is protected and cannot be called from an arbitrary BrowserTest test command.
Please expose waitForJavascriptCallback() as public.
The text was updated successfully, but these errors were encountered:
Can you elaborate a bit on what your test will do? I don't assume normal end users will be typing callback function's in the browser's console window. ;-)
To achieve the goal of readable and maintainable tests I always found that creating a Java subclass of BrowserTest that offers a method that wraps some complex JavaScript implementation of a test-step a good trade-off.
If you want to do your JavaScript directly from the wiki, doesn't (the publicly available) execute script method or (executeJavascriptUntilIs) suffice?
Tests of web-applications that create data grids & histograms sometimes require asynchronous JavaScript calls to the presentation vendor's API, for instance, with Tableau.
waitForJavascriptCallback() is protected and cannot be called from an arbitrary BrowserTest test command.
Please expose waitForJavascriptCallback() as public.
The text was updated successfully, but these errors were encountered: