- 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.
- What are the actual advantages of using this platform instead of coding your own automated tests?
It's fast and easy, you can create your first tests in just a few minutes.
Run your tests in our cloud infrastructure. We provide a wide range of platforms, operating systems, browsers and devices.
Safely store all your tests in our cloud. Access them from anywhere.
Lots of features, such as generating random input data, duplicating tests and taking screenshots.
Activity section. Easily track the latest changes for your test suites.
You can also export your tests in a variety of different formats. Run them on any environment.
- 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:email@example.com).
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.
- 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.
In the 'Upload File' step, you will also have to add the online path for your file.
- 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.
- 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 automated tests for?
Currently, you can create and run automated tests for Web and Mobile Applications using our platform.
- 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).
- What can I see in the Activity section?
The Activity 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?
In the Results section.
- 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.
- I have a really complex scenario and I need to write some of my own code in the test, is that possible?
Yes, all you have to do is Export the test suite as a Python file.
- 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 page.