G2

Pratik S.

Senior QA Engineer

Information Technology and Services

Mid-Market (51-1000 emp.)

10/28/2026

"From "can't reproduce" to "here's exactly what happened""

4.5/5

What do you like best about Sentry?

As a QA engineer, the phrase I dreaded most was "can't reproduce." Sentry has mostly killed it. When I find a bug, the stack trace, breadcrumbs and device details are usually already there. I paste the issue link into my ClickUp ticket and the devs have the full picture. Session Replay on our web app is my favourite part. Watching exactly what someone clicked before things broke saves a ton of guesswork. It covers our Flutter app too, so web and mobile errors are all in one place. Review collected by and hosted on G2.com.

What do you dislike about Sentry?

It's noisy at first. Until we tuned our alert rules, we got pinged for harmless stuff like browser-extension errors and flaky connections. The UI has a lot on it, so it took me a while to feel at home in the performance and release views. Getting readable stack traces from our obfuscated Flutter builds also took some trial and error, since you have to upload debug symbols. Review collected by and hosted on G2.com.

What problems is Sentry solving and how is that benefiting you?

Mostly, it catches the bugs nobody reports. On one project, a background sync to NetSuite was quietly failing for certain orders. Everything looked fine on screen, but Sentry flagged it the same afternoon and we fixed it before the client noticed. It's also changed how I check fixes. After a release I look at whether the issue comes back, instead of just retesting the happy path. I write bug reports faster, there's less back-and-forth with devs, and release days are much calmer. Review collected by and hosted on G2.com.