Comments on: Testing HTTP Callouts

By: Scott Hemmeter

Scott Hemmeter — Thu, 27 May 2010 15:23:26 +0000

I am pretty sure it’s no issue. In the next transaction, the variable is reset. Every transaction is unique so the next callout has its own set of variable instances.

By: codeulike

codeulike — Thu, 27 May 2010 15:15:07 +0000

Is using the static variable like that thread-safe? What happens if someone else calls the call-out at the same time you’re running the test? Or afterwards, for that matter, given that you don’t seem to set the flag back to false?

By: Calling a REST Web Service (JSON) with Apex | Jeff Douglas – Technology, Coding and Bears… OH MY!

Wed, 06 Jan 2010 12:23:00 +0000

[...] unit tests for callouts can present a challenge. Scott Hemmeter has a really good article entitled Testing HTTP Callouts which should provide you with some useful techniques. You should also check out An Introduction to [...]

By: Gabe

Gabe — Thu, 13 Aug 2009 15:54:08 +0000

Great idea dude. So much better than any of the SFDC developers could give me. Web services are obviously still a big mystery to them.

By: Rajesh Shah

Rajesh Shah — Mon, 18 May 2009 10:05:50 +0000

This is a nice way to handle test methods for Apex Callouts. However I would still prefer the other way of dividing the HTTP callout into 3 methods. This way I am not adding any extra code to what is actually required to run the method. All my extra stuff required for testing the callout is in the test method. Another reason is that it is good to have the callout modularised into 3 separate parts. This allows me make the call from different functions and send the response to a single function.

By: Jeff Douglas

Jeff Douglas — Mon, 04 May 2009 18:38:09 +0000

Very nice way to work “with” the Salesforce.com test framework. I tip my virtual hat to you sir.