Florence Healthcare cuts test failure triage time by 75% with BrowserStack Test Observability

Florence Healthcare faced a significant challenge in ensuring the quality and stability of its diverse software portfolio. With five UI test projects and two API projects, the nightly regression suite execution involved executing 4,000-5,000 test cases across different platforms and browsers.

The reporting process using Jira X-Ray lacked historical context, making it challenging to identify persistent issues or trends. “We didn’t have any quantification or metrics, any KPI, or any number for that. We only had how many tests were failing and how many tests were passing. It was very tough to present the progress to our stakeholders. So it was a no-brainer for us to move to Test Observability,” Mile explains.

The sheer volume of test cases led to a time-consuming and cumbersome review process every morning, posing a substantial demand for a streamlined test reporting solution.

To address their testing challenges, Florence Healthcare started using BrowserStack. Mile and his team use the comprehensive suite of BrowserStack products, including Live for manual testing, Automate for web, mobile, and desktop testing, App Live for manual testing of mobile applications, and App Automation for automated testing of mobile native applications.

The implementation of BrowserStack Test Observability especially played a pivotal role in streamlining the testing process. “With BrowserStack Test Observability, we have all our tests and QA projects in one place. That’s the biggest benefit,” Mile adds.

And the benefit doesn’t stop there. “Test Observability is changing how we deal with failing test cases. If we have a test case that is failing because of an environment issue, and if we tag that test case with the environment issue, tomorrow if that same test case fails at the same test step with the same error, Test Observability automatically tags that test case failure cause correctly,” Mile explains.

Test Observability provided a unified platform for all QA projects, offering transparency and efficiency. Its capability of consolidating all kinds of logs, including video, screenshots, CI console logs, framework logs, network logs, etc., was a game changer for the team at Florence Healthcare.

Mile elaborates, “What we like about BrowserStack Test Observability is the easy implementation. Second, the integration with services. The ability to just click on some test cases and bring up a video from that test is very powerful. I don’t know if any other tool has that.”

The impact of BrowserStack Test Observability on Florence Healthcare’s testing efficiency was immediate and profound. “Test Observability has significantly reduced our test failure triage time by around 75%, allowing QA teams to focus only on new and relevant test failures,” says Mile.

The transition to BrowserStack Test Observability as a test reporting tool was multi-fold. It streamlined QA operations, improved clarity on product stability, and fostered transparency across the company. “Stability is the number one thing for us. With BrowserStack, we are tracking the time needed for test executions. That’s the KPIs we care about, and Test Observability helps us track and improve them massively.”

With a centralized hub for all testing processes, Florence Healthcare experienced a boost in overall efficiency, reducing the time spent reviewing test cases significantly. “To go through all test cases and test executions for all our QA projects, I would have needed 1 hour before. With Test Observability, I need a maximum of 10 minutes,” he mentions.

The implementation of BrowserStack Test Observability not only addressed the immediate testing challenges but also empowered the team to prioritize stability and transparency in their testing processes. “Without BrowserStack Test Observability, it would be a big step back for our team,” he says, signing off.