Can multiple users work on the same test suites?

Yes, multiple users can easily work on the same test suites.

To grant a user access to your tests, just use the Collaborators functionality.

How can I run tests for a Web Application that is accessible only from my workplace?

The easiest way would be to whitelist our list of Secure Gateway IPs:

If your Web Application requires HTTP Basic Authentication, just add the username and password in the URL:


All the user agent strings from our cross-browser cloud infrastructure contain the string 'endtest' at the end.

The second option would be to Export the test, but you will be able to run it only on your local infrastructure.

The third option would be to go with our On-Premises version, which is part of our Enterprise Plan.

Do I need to add Waits for any steps?

No, there is no need to add any Waits, since our engine can automatically detect when to wait before executing a step.

We do offer you the flexibility to modify the Element Load Timeout and Page Load Timeout values for each test suite in the Advanced Settings section.

What kind of applications can I create tests for?

You can create and run tests for Web and Mobile Applications by using our platform.

I'm running a test for a Web Application and Endtest can't find an element. What can I do?

You can create and run tests for Web and Mobile Applications by using our platform.

Our engine is using Selenium to find the elements in a Web Application.

1. Use a different locator type.

For example, if you were using Class Name, you can try with XPath or CSS Selector.

2. Is the element included in an iframe?

In that case, you need to add a "Switch to iframe" action. After you're done interacting with that element, you can return to the main context by adding a "Switch back to main" action.

3. Is the element covered by another element?

In order for Selenium to find and interact with an element, it must be visible. You can hide the element that is covering your target element by using an "Execute JavaScript" action.

4. Is the element located in a different browser tab?

You can easily switch by using the "Switch to next tab" and "Switch to previous tab" actions.

5. Make sure that your locator is unique.

If our engine finds more than one element with that locator, it will just go with the first one, which might not be the one you're interested in.

6. Try to identify what makes the element unique.

The element might have a certain attribute that has a certain value, you can write an XPath which locates the element by using that attribute, like this:

'//*[@my_attribute = 'the_value_from_my_attribute'] '

You can also write an XPath which locates the element by using only part of the value of the attribute:

'//*[contains(@my_attribute, 'a_part_of_the_value_from_my_attribute')]'