Wika linked to this website…

I like to look around the web, often I will go to Stumble Upon and read and check stuff out…

While checking out DIGG yesterday I noticed this…

E.g.

public Account getTestAccount() {
Account testAccount = new Account(name = ‘test’);
try {
insert testAccount;
return testAccount;
} catch(Exception) {
return [select id from Account order by lastModifiedDate desc limit 1];
}
}

Another option to consider would be to use a custom setting which for most intensive purposes behave like sobjects, but can’t have validation rules defined for them.

A final option would be to choose to see if you can find a standard object that can be inserted but can’t have validation rules defined against it. Static Resources are one object that comes to mind, but I imagine there are others.

You’re custom object approach makes complete sense, although I’d worry about administrator’s accidentally breaking it as you suggest. IFIRC one of the original versions of CMSForce used a test custom object called aptly enough Test__c that was used in its test methods. However administrator’s had a tendency to delete the object (it was only referenced dynamically) blocking any future deployments (package was unmanaged).

At Dreamforce last year project management mentioned that test methods to side step validation rules and required fields were on the drawing boards but still in very earlier phases. Hopefully they’ll figure this out sooner than later although I’m not holding my breath.

Hope things are going well over at EDL. I still got a stack of cert assignments to work through if you ever get border .

Do you plan to post this library up on GitHub anytime soon?

I call using apex-lang happy fun time.

It makes life so much easier! Keep up the good work!

e.g. SELECT Department__c, COUNT(id) FROM Consultant__c GROUP BY Department__c

Otherwise, thanks for coming up with this. I’ve been using it a lot since I discovered it a few months ago.