#Test horizon apex code#

We are committed to staying ahead of what you create – and you have proven time and again to be very creative and prolific. In addition, we must be prepared for another doubling of transaction volume every several months. With every release, we verify that you still see equal or better performance to what you saw in the past. The development team spends a large amount supporting the growth in Apex transaction volume. Now that this volume is here, it is becoming necessary to modify some of the original assumptions and make changes like this one. This kind of volume was way beyond the horizon when the language was initially created, when it was conceived as a database triggering mechanism. This is more than double what we saw a year ago.

We are running almost 6 billion Apex transactions a month. Thanks to everybody out there reading this, Apex is growing like crazy. So, why the new pattern? This change is a part of our ongoing effort to support the growth of Apex. But first, some background… We’ve Come A Long Way There is a direct benefit to this change in our caching strategy, and this is the first part of some new enhancements to our testing framework you’ll see over the coming year. The check is done at compile time, so if you don’t need to change anything or recompile anything, you will not notice any difference. The new pattern needs to be followed for new classes written in v28.0 and above, and for any classes for which you change the version from an older version to v28.0 or later. If you’ve created tests in executable classes, these will continue to compile in the Apex version in which they were created.

#Test horizon apex code#

To start, let me reassure you that your existing code does not need to change.

This is a departure from the pattern we’ve used for the past six years, and I am sure many people are scratching their heads and asking why we are enforcing this new coding pattern. (A “test class” is one marked with the annotation.) Test methods will no longer be able to compile in the same class as your regular executable code. Starting with the Summer ’13 release of the platform, Apex test methods need to be created in test classes.