Integrate other tools with Test Observability
Integrate commonly used tools with Test Observability to simplify your testing experience.
View server-side application error logs and stack traces by integrating application log collectors like Filebeat, Logstash, Promtail, Fluentd, or Winston.
With automatic integration with SCM tools like GitHub, GitLab, and Bitbucket, you can view the code changes associated with a build directly on Test Observability.
You can re-run any failed tests in your test suites directly from Test Observability by integrating CI tools like Jenkins and Azure Pipelines.
Do more with Test Observability by integrating other tools
QA teams often have to switch between several tools for their daily work. This process can become tedious and inefficient in the long term. You can reduce the need to work with multiple tools by integrating your commonly used tools with Test Observability.
By integrating other tools, you can unlock many features in Test Observability. These features improve your testing workflow and efficiency.
You can activate the following features in Test Observability by integrating other tools:
View backend application logs: Standard logs from testing frameworks record only the client-side errors. In Test Observability, you can also include application logs such that you can see both client-side and server-side logs in one place. With errors and stack traces from both sides available on Test Observability, you can easily investigate what went wrong without the need to manually pull up server logs or cross-check with multiple tools. This convenient method makes debugging a lot easier.
To include application logs, you need to integrate an application log collector like Filebeat, Logstash, Promtail, Fluentd, or Winston. Learn more about integrating application log collectors here.
View source code: You can view the test code on Test Observability without switching to any other tools. This feature helps you know the expected flow of the test case right from Test Observability. You can also click the commit associated with a build to navigate to your SCM tool to inspect what was changed in the code.
Learn more about viewing source code and code changes from Test Observability here.
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.
Report bugs on Jira: When you spot a bug, you can directly report it on Jira without leaving Test Observability. Test Observability automatically adds rich Metadata to the Jira bug such that anyone who looks at it gets all the information needed to resolve the bug.
Learn more about integrating Jira with Test Observability here.
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.
Curious to learn more?
Check out the demo sandbox to experience advanced testing using Test Observability.