[SalesForce] Test Data – Static Resources

I can reproduce the error (which is a pretty clear anyway) so you will need to use ContentType of "text/csv".

I can think of 2 ways of getting the ContentType (labelled "MIME Type" in the UI) to be the required "text/csv":

• Install a different browser and use that to do the uploads as AFAIK it is the browser that infers the content type from the file extension and/or file content; Chrome on a Mac uploads a CSV file with the file extension .csv as "text/csv".
• Use the Force.com IDE or the Ant migration tools to download the static resource(s), then fix the contentType element in the .resource-meta.xml file(s), then upload them. (I used the Force IDE to turn my working "text/csv" static resource into a failing "text/comma-separated-values" one.)

You may have to limit the number of records you create, even down to one per type. If it's still hitting the limit at that point, you're pretty much SOL. As a last resort, you can use SeeAllData=true so that you aren't hitting triggers. Test.loadData won't really help as it still fires triggers.

One solution you can implement as you build out your org (which may be more difficult to implement with existing functionality) is to build trigger stop flags into your handler pattern. My template looks something like:

public with sharing class LeadTriggerHandler
{
    @TestVisible static Boolean bypassTrigger = false;

    final List<Lead> newRecords;
    final Map<Id, Lead> oldMap;
    public LeadTriggerHandler(List<Lead> newRecords, Map<Id, Lead> oldMap)
    {
        this.newRecords = newRecords;
        this.oldMap = oldMap;
    }

    public void beforeInsert()
    {
        if (bypassTrigger) return;
        //LeadSerivices.method1(newRecords);
    }
    public void afterInsert()
    {
        if (bypassTrigger) return;
        //LeadSerivices.method2(newRecords);
    }

    public void beforeUpdate()
    {
        if (bypassTrigger) return;
        //LeadSerivices.method1(newRecords);
    }
    public void afterUpdate()
    {
        if (bypassTrigger) return;
        //LeadSerivices.method3(newRecords);
    }
}

Then in your test you can just do:

LeadTriggerHandler.bypassTrigger = true;
insert new Lead(/*data*/);
LeadTriggerHandler.bypassTrigger = false;

This flagging strategy can dramatically streamline your tests, and can be implemented in a variety of ways. The key is that the flag is static, though I think it is important to keep it private if at all possible.