The application types “Browser (Installed)” and “Mobile Browser” (WAI-ARIA Connector) allow using the installed web browsers directly. WAI-ARIA tags identify the several elements of the web page. Currently Fabasoft app.test can use the following browsers
There are a few settings required on the browsers or systems. Apply the settings on the test clients directly. For each browser there is a Fabasoft app.test web browser extension.
All required files for installation are either available via a public repository or are located inside the folder jsadaptor of the installation directory of the app.test agent or the eclipse installation
To be able to test HTTPS, generate an own certificate as described in chapter “Certificates” or add apptestca.pem to the trusted root certification authorities.
The Chrome extension is in the Chrome Web Store:
The Edge extension is in the Microsoft App Store:
Connecting to localhost must be possible. Enable this with this command:
CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe"
The Mozilla Firefox extension is called mozillafirefoxwebextension.xpi.
The Microsoft Internet Explorer extension is installed by starting microsoftinternetexplorerbho.msi.
Install the plugin by dragging the file Fabasoft app.test Safari Extension.app into the Application folder.
Add apptestlocal.pem to the keychain. Select “Always Trust” for these certificates.
The address 127.0.0.1 must be reachable from the browser and therefore must not be routed through the proxy. Fabasoft app.test uses the system proxy settings when not explicitly configured otherwise.
When using the WAI-ARIA Connector with a Fabasoft Folio or Fabasoft Cloud domain make sure to specify the full URL, including the ax parameter.
When using the WAI-ARIA Connector to test a custom website it is necessary to specify the Basic Authentication URL containing the relative path to the apptestbasicauth.html.
When testing secure web sites using HTTPS a certificate for 127.0.0.1 has to be issued to enable Fabasoft app.test to interact with the secure site. The path to this certificate in PKCS #12 format along with the corresponding password can be configured in Fabasoft app.test in the settings of the selected web browser.
While such a certificate is included in a Fabasoft app.test installation you might want to create a self-signed certificate for the test hosts yourself. This can be accomplished with the tool openssl () following these steps:
openssl genrsa -out cert.key 2048
openssl req -new -key cert.key -out cert.csr -config openssl.cfg
openssl x509 -req -days 9125 -in cert.csr -signkey cert.key -out cert.crt
openssl pkcs12 -keypbe PBE-SHA1-3DES -certpbe PBE-SHA1-3DES -export -in cert.crt -inkey cert.key -out cert.pkcs12 -name "Fabasoft app.test Local Test Certificate"
The resulting PKCS#12 file can then be used by Fabasoft app.test to test secure web pages.
Additionally, this certificate has to be trusted by the web browsers on the test host. It therefore has to be added to the certificate store of the web browsers you wish to use for testing.
Note: On Microsoft Windows operating systems with Microsoft Internet Explorer or Google Chrome the certificate has to be added to the test users’ personal certificate store. Mozilla Firefox has its own application specific certificate store. On Apple OS X the certificate has to be added to test users’ personal keychain and configured to always trust this certificate for SSL connections.
Also, the certificate of the website being tested has to be trusted on a browser or system level (i.e. you have to import the corresponding certificate) if your websites’ certificate is not signed by a certificate authority. Otherwise most web browsers will not allow a connection without user interaction.
If the tested web site or web application is enriched with coverage information using JSCover the WAI-ARIA Connector automatically collects the coverage information before closing a browser session and stores it adjacent to the report of a test run.
In some cases it might be useful to know the language of the web page or even of a specific control as defined in the lang or xml:lang attribute. This can be achieved with the “Language” option of a set statement.
<Set parameter='lang1' location='WINDOWS' options='Language' />
<Set parameter='lang2' location='WINDOWS.alert[text "Cloud"]' options='Language' />
<div id="pluginalertheader" role="alert">
lang1 = de
lang2 = en