BrowserStack Observability Usage Review
November 05, 2024

BrowserStack Observability Usage Review

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Software Version

Enterprise

Overall Satisfaction with BrowserStack

We use BrowserStack observability in our organization. We use to track test reports for regression suite for various products in our org. It gives a nice GUI for all test runs and health status for a given suite and charts out time series test performance along with other metrics. The thing it lacks it understanding between a test rerunning as part of retry logic in TestNG, as currently it counts failure even if in retry the test is passed. It also has some issue with correctly understanding skip tests as it runs/counts that as well even when run is set to false. Support for other frameworks like Spock should be included.

Pros

  • Reporting
  • Charting
  • Health status
  • Failed test labelling

Cons

  • Skipped identification
  • Retry run identification
  • Other framework inclusion
  • Reporting
  • Slack integration
  • Test/Build Health
  • Quick Health Check of product
  • Areas of concern highlighted
  • Testing trends gives alert
Lacking visibility into test health status. It was difficult to consolidate different test suite and share reports with others. Slack reporting was not as useful and lacked insights. Configuring Alert was not possible. Understanding of flakiness was not as visible and being ignored sometimes. Also new failure vs old failures identification was difficult
  • Test Observability
It helped in consolidation of different test reports and giving a visibility of testing trends. Slack integration gives test result as part of CI/CD which is nice to have. Labelling of different test in different category is useful in quick identification of required tests to look into. Historical run result gives idea on when a particular issue starts appearing which is helpful in fixing issue

Do you think BrowserStack delivers good value for the price?

Yes

Are you happy with BrowserStack's feature set?

Yes

Did BrowserStack live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of BrowserStack go as expected?

I wasn't involved with the implementation phase

Would you buy BrowserStack again?

Yes

It is well suited for reporting test runs for different aspect of product with it's observability suite. It labels test health status well along with labelling of it.
The thing it lacks it understanding between a test rerunning as part of retry logic in TestNG, as currently it counts failure even if in retry the test is passed.

Comments

More Reviews of BrowserStack