2017 October Release

Add Fabasoft app.test support to your Web PagePermanent link for this heading

Fabasoft app.test calls the URL to test with the additional URL parameter

apptest.fabasoft.com

If it is defined (the content is not needed to be interpreted by the embedder), the Fabasoft app.test JavaScript Adaptor API script file must be included in the web page, e.g.

<script type="text/javascript" src="[path to apptest.js]"></script>

This script file is originally located in the Fabasoft app.test installation (Studio or Agent): /jsadaptor/api/apptest.js. It must be made available on the web server.

The script file can also be included into the web page even if the apptest.fabasoft.com URL parameter is not defined. The script checks itself if the Fabasoft app.test JavaScript Adaptor has to be loaded or not.

To support multiple windows, the Fabasoft app.test JavaScript Adaptor must be loaded into every opened window. The apptest.fabasoft.com URL parameter which is added to the initially launched URL is not required to be forwarded to all opened windows, but for your own convenience it is recommended to do so.

By default, the apptest.js API file loads the Fabasoft app.test ARIA connector (see the bottom of the script file). You just have to provide the original apptest.js file on your web server and support the ready state indicator JavaScript variable g_pagebusy as described below.

Ready StatePermanent link for this heading

The Fabasoft app.test ARIA connector determines the web page ready state by checking the global JavaScript variable g_pagebusy. The page is only ready (after web page startup or performing an action) if this variable exists and has the value true. If you want to use the Fabasoft app.test ARIA connector, you globally have to provide this ready indicator variable on all pages.

Implement your own ConnectorPermanent link for this heading

If you want to implement a custom connector to test your web page, you can modify the apptest.js API file on your web server. Search for the line containing the connect call (com_fabasoft_apptest_jsadaptor.JSAdaptor.connect) and adjust the paths to your connector files and the constructor expression. The paths can point to files on your web server, relative to the page where test apptest.js file is included.

Implementation of Connector InterfacesPermanent link for this heading

To implement an own connector, you have to provide a TypeScript class which implements the com_fabasoft_apptest_jsadaptor.IConnector interface and subsequently a class which implements the com_fabasoft_apptest_jsadaptor.IControl interface. The doAction method of IControl returns objects created by the (static) methods done, error or warning of the com_fabasoft_apptest_jsadaptor.Result class.
If you do not use TypeScript you also may provide a JavaScript object which provides the methods defined in the interface. The connector object will be instantiated without parameters passed.
How to implement the methods required, see the TypeScript interface definition files itself. The files are located in the jsadaptor directory of the Fabasoft app.test installation (Studio or Agent).

Basic AuthenticationPermanent link for this heading

To provide basic authentication, the apptestbasicauth.html API file (/jsadaptor/api/apptestbasicauth.html) must be made available on your web server. The script sends the credential information via an XMLHttp-Request to your web server and if succeeded, redirects the browser to the application URL. The script must originate from your web server as the authentication request is only possible from the same origin. It must be reachable anonymously. There are no modifications on the file required.

When launching the browser with Fabasoft app.test, the URL to this file (relative to the application URL) must be configured in the browser tab of the run dialog (Configuration Run.browserbasicauthurl).