Yes, you can use Usetrace as long as your server is connected to the internet. See the Network Instructions for details.

Many customers with similar experiences with Selenium have found success with Usetrace.

You should be able to create your first trace in 5 to 10 minutes after registration. To create your first trace, see our 3-minute “First Trace” tutorial.

You can also run your tests against your own laptop or development computer using a tunneled connection to make your web server publicly accessible. See Tunneled Connection to learn more. This flexibility benefits QA engineering teams that need versatile testing automation.

• Automated screenshots
• Javascript extensions
• Cloud service - no installations required
• Download files
• Integration with different CI systems
• Parameterizable (test data)
• Recorded playback - no programming skills required
• Regression testing, production monitoring, and load testing
• Reusability of routines (modular test design in traces)
• Data testing
• Email testing (e.g. email verification)
• Test reporting to email and chat
• Upload files

Usetrace’s automated tests, called traces, are created by interacting with your site as your users would. These interactions, such as clicks on buttons and checks (elements visible on the page, e.g. text), are recorded into reusable routines, building a maintainable automation test suite for your application’s user interface. This is why Usetrace is especially useful for teams looking for automation testing tools without coding.

Usetrace automates functional end-to-end UI testing on website apps. It helps you ensure that the features visible to end users work as expected. Usetrace includes regression testing, production monitoring, performance, and load testing, making it an essential tool in QA engineering.

To set the default base URL for all your traces, exit the Editor and enter your base URL in the upper left corner next to the Usetrace logo. For a specific trace, see the instructions on Custom base URL.

Sign in to your Usetrace account and navigate to Preferences > Project.

All your interactions are recorded and become steps in your trace. Completing each trace with a “Check” is recommended to ensure the feature functions. 

For example, a trace checking the functioning of login should include these steps: clicking the login button, filling in the login form, clicking “login”, and creating a check for “logged in as…” After a “Check” in place, click “Run trace” to test that the entire trace works. Watch the “First Trace” tutorial to see how to automate testing for login.

A trace is successful if it runs through without errors. If any one step fails, the entire trace run is considered a failure.

Change your enabled browsers under Preferences -> Project. To change the API call browsers, see HTTP Rest API for documentation. 

Yes. Take a look at Step types for automating hover menus as an important aspect of browser testing.

Start by creating a check step. Then, press “Configure locators” on the check step and scroll down to “Check for: Text”. Finally, ensure the word “random” is included in the field. See the tutorial Random User for details.

Use the same input string in multiple text fields. Usetrace will use the same randomly generated string for all the referenced text fields. Read Step types for more information.

You can talk to your APIs via JS-step inside your trace. Here’s an example Javascript.

Usetrace browsers come from the IP addresses “52.213.205.23, 52.209.16.51 and 54.78.145.195”.

In Google Analytics, you can filter this IP out by 1) going to Admin -> Account -> All Filters -> + NEW FILTER

• Filter Name: Usetrace
• Filter Type: Predefined
• Select filter type: Exclude
• Select source or destination: Traffic from the IP addresses
• Select expression: that are equal to
• IP address: 52.213.205.23, 52.209.16.51 and 54.78.145.195
• Apply Filter to Views: Add the wanted available views to Selected views

2) or by going to Admin -> Filters -> New Filter -> Exclude IP addresses 52.213.205.23, 52.209.16.51 and 54.78.145.195 and on the same page in Apply Filter to Views: Add the wanted available views to Selected views.

There are three possible reasons for this error. 

First, the locators may not match. See “Configure locators” in the failed step and verify that the locators are correct. Usetrace locators are css, id, name, xpath, and link_text. See the W3School documentation for CSS and XPath to learn how to write these locators manually. 

Second, the locators may match too many elements. Hence, Usetrace does not know which element to click. Write more specific locators for your step.

Third, the locators may match, but the clicking fails. This may happen, for instance, because the element is covered by another element or the element is not visible.

Currently, you can export your project (with all your traces) to JSON.

Logout, go to https://usetrace.com, click “LOG IN,”then click “Forgot your password?” Enter your email and click reset. You will receive an email with the password reset link.

 Alternatively, go to https://team.usetrace.com/#reset-password and fill in your email.

Usetrace transparently handles iframes (even nested iframes), and you don’t have to worry about them when recording traces.

Navigate to tracelist and, from the bottom of the page, click on the recently deleted traces. You can then undelete traces from that list.

You can mask any input data using trace parameters. Expand the parameter tab of the step you want to mask. Replace the sensitive credential in the default value field with a placeholder value (any value). Now, note the parameter name, this is the parameter you need to define in an API call to execute traces. See the API documentation to learn how to define parameters for trace runs. Using this method, your credentials are not stored inside Usetrace cloud, but passed only inside API calls.

We’ve built Usetrace on top of Selenium. It is modular in a similar fashion to programming parameterized modules: traces use reusable routines. Usetrace combines the benefits of programmable tests with the ease of record and playback without requiring programming skills.

Most teams don’t have the required skills for scripted test automation. Even teams with these skills struggle to have time for testing: when software is released daily, scripted tests constantly lag behind development. A simplified testing tool that allows easy test creation and maintenance without programming is needed. However, traditional record & playback tools are inadequate for agile teams due to their maintenance burden. Therefore, Usetrace brings concepts from scripted testing that are available to non-programmers.

Using the Usetrace.com web app is supported by the following browsers:

• Google Chrome
• Firefox
• Safari
• Microsoft Edge

However, you can test your own site using all the supported virtual browsers

We support testing with virtual browsers using the following:

Chrome*

Firefox*

*For latest version details, check with us using the customer support chat. Note that Usetrace is built on Selenium and may not be able to support any higher browser versions than Selenium.