Skip to main content

3 posts tagged with "tracing"

View All Tags

· 2 min read

I am excited to announce the availability of two new features today.

Distributed Tracing

We also rolled out support for distributed tracing with OpenTelemetry traceparent header (W3C trace context specification). Distributed tracing can now be enabled for Browser Tests or API Tests. When distributed tracing is enabled for a Test, the test results section will show a unique Trace ID that can be used to trace the transactions in your distributed tracing tool.

Here is an example Trace ID generated for a Browser Test:

Trace ID

By using the Trace ID, the requests, their latencies, performance, associated logs and other data can be traced. The screenshot below is a view from Google's Cloud Trace (the tool we use) showing the Trace view for the executed test.

Distributed Trace


Services allow you to quickly visualize the Service Health based on the status of associated checks. Services can be associated to SSL Monitors, API Monitors, Browser Tests or even one or more Collections. When an associated test or a test that is part of an associated Collection fails, the Service status will be changed to reflect the failed test.

Here is an example Overview page for Services in a Workspace.

Service Overview

· 2 min read

A browser test recorder has been one of the most asked features by our customers. Today I have happy to announce the launch of DevRaven Recorder.

DevRaven Recorder is a free chrome extension that you can install to quickly and easily record a brower test. The extension automatically generates the code for your test scenario as you perform the operations and the generated code can simply be copied to setup a synthetic monitor for your scenario. Zero coding skills required!

The extension currently supports the following features.

  • Captures mouse interactions including click, hover, double-click.
  • Captures data inputs to input fields such as text fields, password, single and multi-select fields and textarea fields.
  • Captures interactions with checkboxes and radio boxes
  • Captures keystokes including Meta(Command), CTRL, ALT (Option) keys.
  • Detects page navigations such as full web page, SPA or hash change events and automatically waits for navigation to complete.
  • Support for capturing screenshots while recording the tests.
  • Support for adding waitForSelector.

Here is a demo of the recorder in action:

We have also decided to open-souce the extension under Apache 2.0 license. If you are interested in contributing, feel free to send a pull request. The git repo for the extension is available at


The extension will be available on Chrome Web Store very soon following the review process. However you can side-load the extension today to try it out. Just follow the installation instructions available at There is a recording as well for the installation process.

· 2 min read

Developers and Quality teams spend lot of resources to automate the testing and monitoring of their web applications. It's pretty common to see failing network calls or console error messages, even if all the automated tests just pass.

These failing network calls or errors can happen for varities of reasons. It's just humanly not possible to keep track of network failures/errors while executing your tests all the time and also executing the tests from multiple locations. So, these errors just go unnoticed until a customer reports an issue.

Today we are introducing tracing capabilities that allow automatic capture of network requests and console log messages while executing your browser-based tests. Your test could be as simple as logging in and visiting all your application's web pages or you might have a test covering a complex scenario. You will get visibility into all the network requests that happen while executing your flow.

Here are a couple of screenshots:

Network requests: A familiar user interface similar to Developer Tools that allows you to search/filter the network requests.

Network Requests

Console log messages: UI showing console messages with an ability to search or filter the messages.

Console Logs

Refer our documentation for more details on enabling tracing for your browser-based tests.

Other updates:

  • No-code editor now supports executing tests on Chromium, Firefox, WebKit browsers with simple configuration.
  • No-code editor now supports waitForLoadState operation.
  • No-code editor now supports changing waitUntil option for Go To Url operation
  • other minor fixes and enhancements