Compatibility Testing

• Different operating systems your web application supports.
• Different browsers to ensure that certain coding such as Active X Controls, JavaScript, CSS, and HTML function properly across multiple browsers.
• Different languages for localized versions of your web applications.
• Different databases your web application supports.
• Run against different servers, ports and protocols.

Compatibility Testing Features

Multi-platform Support:

For example, if your application runs on both Windows XP, 2000 and Linux, you may want to test it in both the platforms. QEngine allows you to test the functionality and performance of your web applications/web services in both Windows and Linux machines.

Multi-browser Support:

Interoperability between IE/Firefox/Mozilla browsers. Scripts recorded in Microsoft Internet Explorer can be played in Mozilla, Firefox and vice versa.

Multi-lingual Support:

Unicode-enabled script allows you to re-use the same script to playback with any localized version. 18N Editor Tool for Internationalization enables you to configure localized keywords from the map file for the selected suite. You can also make use of the library of functions available to enable localized testing.

Multi-database Support:

You may want to validate and verify the HTML properties with the data retrieved from a database. This database may be specific to your web application and you may have one or more databases to be validated with the same script. QEngine offers a generic database interface that enables you to test multiple databases including MySQL, Oracle, SQL Server or any JDBC-compliant database without changing the scripts.

Run against different servers and ports:

Assume you have 25 scripts in which you have recorded the various actions in your web application hosted in one of the server say test-server1 and in port no 2200 i.e., each script has a url such as "http://test-server1:2200/testapp/index.html". To re-use the same test script to test it with different servers and port, you just have to make the change in a single screen (Host-Port Settings screen), instead of manually editing each and every script. QEngine handles this by dynamically changing the host name and port number in the test scripts during playback. This helps you to run the same test script with any host name and port number without re-recording the test scripts. Similarly, if you have recorded scripts using HTTP protocol and you want to run all the scripts with HTTPS protocol without re-recording the scripts then you can follow the same approach by just making the change in one single screen.