Hello Apex Programmers:
If you are reading this, I can confidently address you as “programmers”, because if not, your eyes would have quickly skipped to the next item when they saw the word “Eclipse”. You, however, are not scared of Eclipse! You stare directly at it. (Note: do not stare directly at a solar eclipse.)
We will release a new version of the Eclipse plug-in for Spring ’13 on February 15th. What’s that, you say? A “silent release” with no officially sanctioned date? And a week or two after the actual release?!? Before you call “shenanigans” on us, please… Continue reading
First of all, I’m happy to see you. If you’re reading this, it means you have written Apex tests and want to run them, which makes me very happy. I’ll explain why in a later blog post, but for now, just know that writing and running tests is good for you AND good for us.
Now to the topic of the hour: Where did my old test result UI go?
You may have noticed that, with the Spring ’13 release, the “Run All Tests” button on the Apex Classes list… Continue reading
I know you are all familiar with code coverage in Apex and the requirement to have 75% of your code covered by automated tests. However, I have heard many questions regarding the different code coverage numbers you see in your orgs. This post should help clear up some of the confusion in how the various numbers are calculated.
We Store Your Code Coverage
The first thing to know is that the system stores data from your latest test runs. Each time you run the tests in a class, an entry is made in the code coverage table for each class… Continue reading
You can execute Apex code from a detail page button in Salesforce, using very basic VisualForce. This blog post offers step-by-step instructions on how, and an explanation of the technology behind it. Continue reading
Your org has a namespace, whether you are doing packaging or not. Here is an explanation of that namespace, and how it is used in Apex. Continue reading
We will be making a change to the Apex documentation on the notion of “pass by reference”. Here is a detailed explanation of why the change is being made.
The current Apex documentation says that non-primitive variables are passed by reference:
“Also note that all primitive variables are passed by value, while all non-primitive data types are passed by reference.”
Strictly speaking, this is not true. The new text will read:
“In Apex, all primitive data type arguments, such as Integer or String, are passed into methods by value