- Why should software testers use this platform instead of just coding their own automated tests?
A software tester's primary focus should always be to come up with test scenarios, not to write code.
This platform allows testers to easily create and run automated tests without writing any code, thus saving valuable time.
Our cloud infrastructure can save you a lot of time and money.
- Can multiple testers work on the same test suites?
Yes, multiple testers can easily work on the same test suites. To grant a user access to your tests, just use the Test Suite Sharing feature.
- 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 (http://username:firstname.lastname@example.org).
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 technology can automatically detect when to wait before executing a step.
- What kind of applications can I create tests for?
Currently, you can create and run tests for Web and Mobile Applications using our platform.
- I'm running a test for a Web Application and Endtest can't find an element. What can I do?
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.
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:
- How do Self-Healing Tests work?
Whenever you run a test, our platform learns more about your application.
If an element from your application is changed and the
test gets broken, our engine will automatically fix the broken steps by updating the locators.
- How do I use the 'Upload File' action?
You can easily perform a file upload in a test on our platform.
First, you must find the input with the type "file" in your Web Application.
That is the element for which you will provide the locator in the 'Upload File' action.
Sometimes, the input with the type "file" may be hidden or may not be displayed.
Depending on the state of your element, you might also need to update CSS properties such as width, height, opacity, z-index, pointer-events, etc.
If you still can't figure it out, just send us a message, we'll gladly help out.
In the 'Upload File' step, you will also have to add the online path for your file.
You can upload your file in the Drive
- How do I get the ID, Name, XPath, Class Name and CSS Selector for the elements from the Web Application that I am testing?
You can easily get those from your web browser, for example, just use the Developer Tools (for Google Chrome) or the Firebug extension (for Mozilla Firefox).
Our engine for the Web Tests is using Selenium, you can read more about finding elements with Selenium here
- How do I get the ID, Accessibility ID, Name, XPath, Class Name, Android UI Automator, iOS UI Automation for the elements from the Mobile Application that I am testing?
The easiest way to get those is by adding "Get Page Source" actions in your test.
Our engine for the Mobile Tests is using Appium, you can read more about finding elements with Appium here
- Can I also create and run tests for Hybrid Mobile Applications with Endtest?
Yes. Hybrid Mobile Applications have two contexts, a native one and a web one. You can easily switch between them with the "Switch to Context" action. If you will add a "Get Page Source" action, you will get different page sources, depending on the context in which you currently are.
- How do I get the Download URL for my APK or IPA file?
In order to install your mobile application on a device, we need to download it from a Download URL.
You can upload your APK or IPA file in the Drive
You can also upload your APK or IPA file on a server or an AWS S3 bucket. The URL must have the file name and the file extension at the end and the file (app) must be downloaded automatically, without any prompts or confirmations.
Take our APK Download URL for the WIkipedia Android App as an example:
- What can I see in the Activity section?
section shows the latest changes for your test suites and also for your user account.
- Where can I see the results after I ran my test suite?
- Is there an API which I can use to run my tests from Jenkins or TeamCity?
Yes. You can find more information about our API on the Documentation
- How can I check if a service from Endtest is operating normally?
You can check the status for our services on the Health Status
- Where can I see the results after I ran my exported test suite?
A text file with detailed results is generated in the same directory every time you run a test suite.
- I have exported and downloaded a test suite, but it shows me an error message when I'm trying to run it, what should I do?
The error message should point you in the right direction. The most common reasons include not opening the file as administrator or not having one or more of the dependencies installed.
In the Export modal, a list of dependencies is displayed for each format that you select. Always be sure that you have those dependencies installed.
- Why would I export my test suite as an executable file?
Exporting a test suite as an executable file means that you can easily run that test suite without installing any dependencies.
- Is the Export functionality related to GDPR?
No, the Export functionality simply takes the test steps that you have entered and converts them to Automated Tests written in Python.
- How can I make a GDPR request?
Users can make GDPR requests by using the Contact Us