I've written an Apex job that makes use of some JobScience objects. I'm having a problem with creating a new JobScience Job Location object in an Apex test class. I can successfully create and insert the object, but what happens is there is a process that is called from within the managed package for that insert (trigger or otherwise) that attempts to make a callout to their Geolocation service which is a violation in Apex test classes (no callouts allowed). My guess is because the object contains a Geolocation field. I've tried to mock this callout (which I really can't do because it's in their namespace), I've tried to pre-populate the Geolocation field (just Lat and Lng) via a call to a mock Geolocation service, and verified that the values are indeed there, to see if that would prevent their callout from happening, but that didn't work either.
Has anyone ever run into this specific case with JobScience Job Locations inside of test classes (or anything similar when working with other managed objects)? I have no idea how to work around this and, unfortunately, Job Location is a required object for this test. We've reached out to their support but they are not able to help us (for a myriad of reasons, we'll just leave it at that).
Thanks for any an all help!