NOTE: Web application testing is currently in the early stages of development. This feature is only available upon request through the chat on the User Experience Insight dashboard or via direct email to support@capenetworks.com. Your request will be evaluated by the User Experience Insight team.

User Experience Insight has always been capable of testing a web server by checking port availability, SSL certificates, and HTTP status codes. This works great for measuring and correlating the performance of the network with the performance of the application. In addition to this data, User Experience Insight now enables you to get a deeper understanding of web application performance from the end-user perspective with the Web Application Testing framework. 

How to Record a Web Application with Selenium IDE:

  • Clear your browser data. This helps prevent web applications from recognizing you have been there before so you can make a clean recording. 
  • Launch the Selenium IDE Google Chrome Extension.
  • Select Record a New Test in a New Project. 
  • Name the project.
  • Enter a base URL and select Start Recording. The web browser will launch 
  • In the web-browser that is launched, perform your interaction with the web page.
  • When finished, select the selenium extension to bring up the recording menu
  • Stop the recording
  • Save the recording
  • Give the test a name
  • Ensure file type is .side:

How to Add a Web Application Test to User Experience Insight

Go to Settings -> Testing and Select Add Test

In the Add Test Menu:

  • Select whether the test should be listed under Internal or External
  • Select Template Type: Custom
  • Select Template: Web Application Test
  • Upload the ".side" file recorded earlier

  • The target field will be derived from the .side file.
  • The Test Title is also derived from the .side file but can be modified.
  • Select the test frequency and select Add 

Web Application Test Results

Web application tests provide the total time the test took to run.

If the test encounters an error, the sensor will attempt to diagnose why the test failed in an automated triage mode. Triage mode will run a set of predefined troubleshooting tests to get the root cause of the test failure and help determine if the test encountered a network problem or application problem. If the triage mode reaches the web application test, the textual output displays the specific problematic web page elements.

Current limitations

This is the first phase in a series of more web app testing updates to come. As a result, there are some caveats/limitations at the moment. These are some of the limitations that will be coming in a future release;

  • Web app testing won't work with a proxy
  • If testing application login, it is recommended to create user accounts specifically for the sensor to test. Using personal credentials is not recommended. In addition the account should not require 2 factor authentication.

See all that's new...

For all User Experience Insight updates, see our updates page, otherwise get started with web app testing today.

Did this answer your question?