How are you guys staying on top of your frontend debugging?I run a small frontend team with 4 engineers, most devs are juniors with less than 3 years of exp. Im the senior guy that puts in place process or tooling. Manual QA is not in the picture due to budget constraints. My team is finding ourselves stretching thin between new features development and existing customer support.
What we have tried:
– Sentry for error reporting. Especially because we can tally exceptions based on volume instead of just hearsay- Posthog tracking for session recording
Why doesn’t it work:
– Mapping which exception in Sentry belongs to which Posthog’s session recoding is a BIG pain
– Sometimes, the UI breaks on lesser used browsers and sometimes, the user goes through such a rare use case that we couldn’t simply replicate (even with a Jira ticket from our support team)
Is there a frontend error reporting tool out there that allows us to see what the users do before encountering an exception, especially if we can filter by volume/frequency of exception? What are your practices to get better bug reporting by the customer support team?
submitted by /u/nhatquang238
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/cDj7QZ3