Starting recently we are now getting this error during tests:
Methods defined as TestMethod do not support Web service callouts
Rather than saying "Test Method Skipped" they are failing and causing deployments to not be able to complete.
The problem is that many of these are due to managed packages that do not implement protection from client tests and do not implement mock interface thus attempting to callout during test methods.
Is anyone else seeing this issue? Anyone found a fix.
Also, the stack trace string is simply blank in the test execution summary. The debug log show a managed package attempting to make a callout
Update Based on Crop's comment I thought I had a workaround BUT alas, the test is inserting / updating a record which causes the managed package to attempt a callout and since it is a trigger I have to have at least 1% coverage so I have to insert or update a record which causes the managed package triggers to fire....Oh vicious circle.
I changed the old trigger to a process builder process which removed the need for the trigger. Still does not solve the problem if it was a more complex trigger....
Implementing the managed Package mock response class still produces the error. It seems that a test.setMock within a local test does not get utilized by the namespaced class making the callout during a test.