FAQ

If you started a trial on January 2, 2020 or later, you are already using the new recorder! Otherwise, you will still be using the previous version unless you have opted in to try the new one. If you have opted in, you will see something like this at the top of the Record a Script page:

Click the image to enlarge it.

Navigate to the Record a Script page and click the Try it out link in the alert near the top of the page. If you need to switch back to the previous recorder, the alert will have that option as well (see screenshot above).

Click the image to enlarge it.

Quicker launch time: The new recorder platform is built on a completely new stack that is not shared with any other test types. This allows it to be very lightweight and results in much quicker launch times!

Record from here: The new recorder has one of the most popular R&R feature requests! When editing a script in the new recorder, you can choose a step and play back the recording to that spot, then start recording new steps.

Smarter element detection: One of the main motivators to switch to the new recorder was LoadNinja’s state of the art element detection. Users will find the new element detection methods much more accurate as it reduces the need to manually set CSS selectors or XPath paths.

Local Connection is a feature we are now supporting for the new recorder; however, it is via CrossBrowserTesting SecureTunnel. Also, bare in mind that there could be delays outside the United States.

Scripts recorded with the previous recorder (v1) will always be available on your account. Editing and replaying those scripts will also continue working as they do now. Accounts that were created before we released recorder v2 will still be able to record new scripts using recorder v1.

In the future, we plan on only releasing new features for the new recorder, and at some point will retire the previous recorder. We will be sure to notify any users that are still using the previous recorder of our intentions before we make that switch. Even after we retire the previous recorder, we will still support editing and replaying those scripts.

Why is it important?

By adding a filter to your reporting tools like Google Analytics, you ensure that QA and automation efforts are not factored into demand generation numbers, prospect website traffic, and so on. This allows your marketing team to report out and optimize their funnel based on correct numbers.

Steps to Exclude the CrossBrowserTesting IP

To exclude the CrossBrowserTesting IP, follow these steps:

1. Reach out to the CrossBrowserTesting Support team via email or chat to obtain our IP address.
2. Sign into your Google Analytics.
3. Navigate to your report view.
4. Select filters and add a new one.
5. Leave the Filter Type as Predefined.
6. Click the Select filter type drop-down menu and select Exclude.
7. Click the Select source or destination drop-down menu and select traffic from the IP addresses.
8. Click the Select expression drop-down menu, and select the appropriate expression.
9. Enter the IP address or a regular expression.

With Java tests, the @ symbol gets escaped almost all the time. Situation is quite common and comes with a simple solution. To fix this, you need to change an email like the following example:

myemail@cbt.com → myemail%40cbt.com