1

I've been building out queueable processes in our Sandbox on Summer '18, and I was able to deploy some of the functionality last week to Production (Spring '18), and now those tests in Sandbox are failing with 'Internal Salesforce Error'.

I have two immediate concerns -

  1. Is it likely, then, that the tests (and possibly the processes themselves) will start failing when Production is upgraded, and
  2. If the sandbox was upgraded ~ a week ago, and I was able to run tests last week in the upgraded sandbox, what's going on?

I don't see any issues on Trust at the moment for my Sandbox instance; not sure what my next steps ought to be to move forward on these projects, since the similar tests for phase two are also failing w/ the same(?) internal errors.

closed as off-topic by battery.cord, Himanshu, Pranay Jaiswal, glls, Brian Mansfield May 14 '18 at 19:02

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on problems in code you've written must describe the specific problem and include valid code to reproduce it. For help writing short, self-contained syntactically-valid examples, see: SSCCE.org" – battery.cord, Himanshu, Pranay Jaiswal, glls, Brian Mansfield
If this question can be reworded to fit the rules in the help center, please edit the question.

  • This wasn't a problem in code per se; there was an known issue w/ Summer '18 API which we discovered after it had been escalated a few times. Thankfully, it was resolved before our Production instance came time for Summer. – Duncan Stewart Jun 29 '18 at 19:33
1

Before each release, Salesforce runs the Apex Hammer Test, which basically means it runs all of your tests in the current release and the next release, and logs any differences in behaviors (e.g. failures, Internal Server Errors, etc). If there is a difference, these differences are given high priority to be patched before the next release hits.

So, what likely happened is that the AHT ran against your org, the error was logged, a bug was generated, and it was patched. This all happens invisibly behind the scenes so customers don't have to worry about it. As far as I can tell, no customer anywhere ever has had a test that passed in one release and fail in the next purely because of regression; Salesforce is really good at catching those errors.

However, if you're really concerned, you can contact support. The most likely course of action is that they'll forward your case to R&D (Research & Development) to get it fixed, or advise you on how you can fix your code so it won't be impacted in Summer '18.

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