Hi Ann,
I stood up a demo instance and populated it with some sample data: https://sonar.overops-samples.com/dashboard?id=com.shoppingcart%3Ashopping-cart-demo
I understand your skepticism regarding our minimal “OverOps Event” rule. Since we’re a dynamic code quality tool, we can’t create predefined static rules for every possible exception or event we find. Instead, this rule is used as a catch all, enabling us to add issues for any event we find. Each issue describes why it was flagged and the link in the comments provides further context.
As an example, here we identify a swallowed exception, or an exception that wasn’t properly handled: https://sonar.overops-samples.com/project/issues?id=com.shoppingcart%3Ashopping-cart-demo&open=AXDpTsxcS9fteZwWKW7A&resolved=false&tags=overops
Thanks,
dave