Skip to main content

Advanced features in Test Observability

Experience the full potential of Test Observability by using these advanced features.

Improve your test suites with advanced features in Test Observability

With Test Observability, you get many powerful tools to improve the quality of your automation test suites.

The following are a few advanced features you can use in Test Observability:

  1. Custom Alerts: You can set up rules on Test Observability on parameters like build stability, flakiness, build performance, and more. Get instantly alerted if a build or project crosses the threshold. Such alerts help you keep a tab on the most important quality metrics of your test suites. You can also set Critical and Warning levels on the same alert to create better workflows to handle quality breaches. Click here to learn how to set up these custom alerts. Demo of Custom Alerts

  2. Smart Tags: SDETs spend a lot of effort locating and classifying problematic tests in their test suites. Test Observability automatically tags tests as Flaky, Always Failing, New Failure, and Performance Anomaly. These Smart Tags help you quickly spot issues in your builds and debug the problematic tests that matter first. You can also configure Smart Tags according to your requirements. Learn more about Smart Tags here. Demo of Smart Tags
  3. Re-run Tests: The ability to re-run tests removes the dependencies on other teams and speeds up the workflow for SDETs. After debugging and fixing a build, SDETs can re-run the build from Test Observability without requesting help from the DevOps team. In Test Observability, you can re-run the tests and automatically map them with previous runs of the same test case.

    You can integrate Jenkins and Azure Pipelines with Test Observability to activate the re-run feature. Learn more about re-running tests here. Demo of Re-run Tests
  4. Automatic Failure Analysis: Bugs largely fall into similar patterns of failures. If these patterns are not recognized, SDETs will have to spend too much time debugging issues that were already analyzed. Test Observability automatically categorizes failures in a test suite into various categories like Product bug, Automation bug, Environment issue, and No defect using machine learning algorithms. This classification helps SDETs to focus on the errors that need immediate attention. You can also track which types of errors are plaguing your test suites and take measures to improve them. Learn more about Automatic Failure Analysis here. Demo of Automatic Failure Analysis
  5. Mute Tests: Test suites often have stale test cases that are in the backlog to be fixed. Stale test cases cause builds to fail and skew the metric calculations and insights that Test Observability provides. While you wait for these test cases to be fixed, you can choose to mute them in Test Observability. When you mute a test case, Test Observability excludes them from the overall build run execution results and all metric calculations. Learn how to mute tests here. Demo of Mute Tests
  6. Custom Views: Views in Test Observability allow you to slice and dice your testing activity based on the criteria that you choose. For example, you could create custom views for different modules of a product. Similarly, you could create views based on factors such as the type of testing, releases, date of test run, test framework, platform used, and many more. Such customized views help you switch between different contexts seamlessly for quicker insights and improved productivity. Learn more about custom views here. Demo of Custom Views

New to Test Observability?

You can integrate Test Observability with your test suite in a few minutes. Test Observability works with most of the leading test frameworks.

Get started now

Curious to learn more?

Check out the demo sandbox to experience advanced testing using Test Observability.

Explore sandbox

Talk to an Expert
Talk to an Expert