I have a custom trigger written on a managed package object. When I run All tests, the trigger shows 100% coverage in SB. However, I am not able to find the class that covers it. I downloaded all the classes in my IDE and searched for the object API name. However, it does not pull up anything.

Also, while deploying to production, it fails.

Can a managed package test class cover a non-managed package trigger? And could it have failed in Production because we ran Default tests?

1 Answer 1


Yes, most, if not all, managed packages end up using their custom objects in test classes, so their tests would count towards your coverage. Obviously, as a best practice, you should write your own tests for the object.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.