Skip to main content

What is Test Observability?

Learn how Test Observability helps you debug root cause of test failures to improve test suite health.

Test Observability attempts to find answers to the following questions faced by SDETs worldwide:

  1. Among the tests that failed, what are the genuine failures and what is just noise?
  2. Can I ignore all the noise and ensure that I don’t miss genuine failures without wasting time doing repetitive tasks everyday?
  3. There are so many test failures but can I get to know how many unique errors is responsible for all of these failures?
  4. Out of the failures that are not noise, can something help me carry out the root cause analysis in a matter of seconds?
  5. I want to know the most unreliable or slowest tests in my suite.
  6. I want to keep track of stability and performance metrics of my test suite over time and get alerted of regressions in behavior, and many more…

Why should you use it?

We’ve tried to list down a few reasons why we think Test Observability would be beneficial to you but the list is endless.

  1. Its super easy to get started and experience the product: You can use the BrowserStack SDKs in different frameworks and integrate with Test Observability in a matter of a couple of minutes.

  2. Debugging is made fun since a lot of repetitive overhead is taken away: Flakiness detection, new failure detection, always failing test detection, and unique error analysis with automatic failure category detection makes real failure identification super intuitive and fast. Following are a few snapshots of the Build Insights from Test Observability that make life easy:

    Build Insights of Test Observability

  3. Unique error detection saves a lot of time in trying to go through a lot of common-cause failures: Test Observability analyzes unique error occurrences in a build run and maps all similar failures together so that you can analyze all such failures together for faster debugging:

    Unique error analysis of Test Observability

  4. Automatic failure analysis helps to intelligently identify failures into different buckets for an assisted debugging experience: Test Observability employs various sophisticated algorithms to intelligently categorize test failures into issue type buckets and this helps to focus on few buckets to ensure no real product bug creeps into production. The following example shows a failure being automatically tagged as a product bug:

    Automatic failure analysis of Test Observability

  5. A complete test report in tree structure with historical test run status, tags, presence of open issues, etc: The detailed test listing view offers rich filters and search options and also presents a quick preview of error and historical data of the same test case as shown below:

    Test listing of Test Observability

  6. Consolidated logs from framework, JS console, network, and backend application along with the video of execution offers a timeline debugging experience like never before: An example is shown below:

    Test details of Test Observability

  7. Ability to re-run specific test cases on CI from the tool: Test Observability offers CI integrations that can be used to trigger re-run of specific test cases right from within the tool. The re-run results are merged back to the original run.

  8. Ability to dive into the git commit or the source code of the test case that failed: Test Observability provides deep integration with git such that it is able to map the source code of the test cases along with its execution such that when in doubt, you can dive into the test case code right from within the tool.

  9. A detailed view of all tests that ran in a project, their stability over a period of time and performance regressions over time: Test Observability also offers x-ray views of test cases from a consolidated run standpoint such that tests can be analyzed over a time period to decide what needs to be fixed and also identify the source of issues by looking at a timeline view. An example view is shown below:

  10. and many more…

Who is it for?

BrowserStack Test Observability is meant for anyone who runs and wants to analyze their automation tests. That said, these are the primary personas who will find the maximum use for the product:

  • SDETs who run functional tests and wants to analyze and improve the quality of their suites.
  • Developers who want to improve the quality of their unit testing suites
  • QA managers who want to analyze the suite health issues to be able to know whats broken and need to be fixed.
  • QA leaders who want to get a general idea about the testing trends in their QA org to find issues and plan ahead of time.

Supported frameworks

BrowserStack Test Observability is currently in private-alpha and it supports the following automation test frameworks but we’re building support for more frameworks at the speed of light:

What next?

Test Observability is currently in private-alpha. If you do not yet have access to the product, you can reach out to us requesting early access.

If you already have access, you can get started with Test Observability in minutes.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked

Thank you for your valuable feedback

Is this page helping you?


We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked

Thank you for your valuable feedback!

Talk to an Expert
Download Copy