Testing web applications

TestArchitect lets you create, manage and run web-based automated tests on different types of browsers.

Supported web browsers

TestArchitect allows you to test web applications in the following browsers and operating systems:

• Windows:

  • Microsoft Edge, version 44.18362.449.0, 42.17134.1.0

    • Microsoft WebDriver Release 14393

  • Internet Explorer: 11

    Restriction: 
    The Modern UI (Metro) version of Internet Explorer 10 and 11 is not supported.

  • Google Chrome, version 129

  • Edge Chromium, version 129

  • Mozilla Firefox, version 130, 131

• Linux:

  • Red Hat 7.2: Mozilla Firefox, up to version 78 Extended Support Release ESR.

    Important: 
    Note that, you are required to install Firefox from the package manager. For details, please refer to the documentation of the Red Hat Enterprise Linux version you are using.

Client and server-side technologies

TestArchitect interacts with web applications through UI controls displayed in browsers; that is, the client side of web applications. Testing does not depend on the application’s server-side implementation. Consequently, TestArchitect allows you to test web applications developed with any client- or server-side technology, including (but not limited to):

• HTML
• HTML 5
• ASP.NET
• PHP
• JavaServer Pages (JSP)
• Java Servlet

Supported controls

TestArchitect recognizes and provides support for various web controls including:

• Standard HTML controls
• HTML 5 controls
• All third-party ASP.NET controls

Test machine and web browser configuration

• By default, TestArchitect Register Server, which is installed with TestArchitect, automatically starts up as a service (daemon) each time you boot your computer. This service is often essential for automated testing, and should generally be available. Ensure the availability of the TestArchitect Register Server service before running your automated tests.
• Before testing web applications on a supported browser, ensure that necessary settings or reconfigurations required by TestArchitect are fully met. For detailed instructions, see Preparing web browsers.

For power-saving purposes, computers are often configured to go into a non-active state (such as sleep) after a certain period of inactivity. By default, the processes associated with automated testing are typically not treated as “activities”, in this sense. Hence, for long execution runs, especially unattended ones, it is important that any machines serving as test controllers be configured not to lapse into any non-active mode during the test period. (Typically, your computer’s power policy is configured through its Control Panel, System Preferences, or command line, depending on the platform. For details, see your system administrator or information specific to the machine’s operating system.)

Automated web testing with non-WebDriver

Automated web testing with WebDriver
WebDriver is a tool for automating web application testing executing tests across a wide range of browsers like Chrome, Firefox and Microsoft Edge. As a member of the Selenium family, it is designed to provide better support for dynamic web pages.

Troubleshooting web automation
A discussion of issues you may encounter when automating tests on web browsers, and possible solutions to these problems. FAQs are also mentioned.

WebKit vs WebDriver
Differences between WebKit and WebDriver